On Mon, Jun 27, 2016 at 09:25:45PM +1000, Balbir Singh wrote:
>
>
> On 26/05/16 16:22, js1...@gmail.com wrote:
> > From: Joonsoo Kim
> >
> > Hello,
> >
> > Changes from v2
> > o Rebase on next-20160525
> > o No other changes except following description
> >
> > There was a discussion with Mel
On 26/05/16 16:22, js1...@gmail.com wrote:
> From: Joonsoo Kim
>
> Hello,
>
> Changes from v2
> o Rebase on next-20160525
> o No other changes except following description
>
> There was a discussion with Mel [1] after LSF/MM 2016. I could summarise
> it to help merge decision but it's better
On Tue, Jun 21, 2016 at 10:08:24AM +0800, Chen Feng wrote:
>
>
> On 2016/6/20 14:48, Joonsoo Kim wrote:
> > On Fri, Jun 17, 2016 at 03:38:49PM +0800, Chen Feng wrote:
> >> Hi Kim & feng,
> >>
> >> Thanks for the share. In our platform also has the same use case.
> >>
> >> We only let the alloc wi
On 2016/6/20 14:48, Joonsoo Kim wrote:
> On Fri, Jun 17, 2016 at 03:38:49PM +0800, Chen Feng wrote:
>> Hi Kim & feng,
>>
>> Thanks for the share. In our platform also has the same use case.
>>
>> We only let the alloc with GFP_HIGHUSER_MOVABLE in memory.c to use cma
>> memory.
>>
>> If we add zo
On Fri, Jun 17, 2016 at 03:38:49PM +0800, Chen Feng wrote:
> Hi Kim & feng,
>
> Thanks for the share. In our platform also has the same use case.
>
> We only let the alloc with GFP_HIGHUSER_MOVABLE in memory.c to use cma memory.
>
> If we add zone_cma, It seems can resolve the cma migrate issue.
Hi Kim & feng,
Thanks for the share. In our platform also has the same use case.
We only let the alloc with GFP_HIGHUSER_MOVABLE in memory.c to use cma memory.
If we add zone_cma, It seems can resolve the cma migrate issue.
But when free_hot_cold_page, we need let the cma page goto system direc
On Fri, May 27, 2016 at 03:27:02PM +0800, Feng Tang wrote:
> On Fri, May 27, 2016 at 02:42:18PM +0800, Joonsoo Kim wrote:
> > On Fri, May 27, 2016 at 02:25:27PM +0800, Feng Tang wrote:
> > > On Fri, May 27, 2016 at 01:28:20PM +0800, Joonsoo Kim wrote:
> > > > On Thu, May 26, 2016 at 04:04:54PM +080
On Fri, May 27, 2016 at 02:42:18PM +0800, Joonsoo Kim wrote:
> On Fri, May 27, 2016 at 02:25:27PM +0800, Feng Tang wrote:
> > On Fri, May 27, 2016 at 01:28:20PM +0800, Joonsoo Kim wrote:
> > > On Thu, May 26, 2016 at 04:04:54PM +0800, Feng Tang wrote:
> > > > On Thu, May 26, 2016 at 02:22:22PM +080
On Fri, May 27, 2016 at 02:25:27PM +0800, Feng Tang wrote:
> On Fri, May 27, 2016 at 01:28:20PM +0800, Joonsoo Kim wrote:
> > On Thu, May 26, 2016 at 04:04:54PM +0800, Feng Tang wrote:
> > > On Thu, May 26, 2016 at 02:22:22PM +0800, js1...@gmail.com wrote:
> > > > From: Joonsoo Kim
> > >
>
> >
On Fri, May 27, 2016 at 01:28:20PM +0800, Joonsoo Kim wrote:
> On Thu, May 26, 2016 at 04:04:54PM +0800, Feng Tang wrote:
> > On Thu, May 26, 2016 at 02:22:22PM +0800, js1...@gmail.com wrote:
> > > From: Joonsoo Kim
> >
> > > FYI, there is another attempt [3] trying to solve this problem in lkm
On Thu, May 26, 2016 at 04:04:54PM +0800, Feng Tang wrote:
> On Thu, May 26, 2016 at 02:22:22PM +0800, js1...@gmail.com wrote:
> > From: Joonsoo Kim
>
> Hi Joonsoo,
>
> Nice work!
Thanks!
> > FYI, there is another attempt [3] trying to solve this problem in lkml.
> > And, as far as I know, Qua
On Thu, May 26, 2016 at 02:22:22PM +0800, js1...@gmail.com wrote:
> From: Joonsoo Kim
Hi Joonsoo,
Nice work!
>
> Hello,
>
> Changes from v2
> o Rebase on next-20160525
> o No other changes except following description
>
> There was a discussion with Mel [1] after LSF/MM 2016. I could summari
From: Joonsoo Kim
Hello,
Changes from v2
o Rebase on next-20160525
o No other changes except following description
There was a discussion with Mel [1] after LSF/MM 2016. I could summarise
it to help merge decision but it's better to read by yourself since
if I summarise it, it would be biased f
13 matches
Mail list logo