From: Vlastimil Babka <vbabka@suse.cz>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>, Laura Abbott <labbott@redhat.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
lsf-pc@lists.linux-foundation.org,
Linux Memory Management List <linux-mm@kvack.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [LSF/MM ATTEND] 2016: Requests to attend MM-summit
Date: Tue, 26 Jan 2016 19:53:45 +0100 [thread overview]
Message-ID: <56A7C0B9.7040701@suse.cz> (raw)
In-Reply-To: <20160126073846.GC28254@js1304-P5Q-DELUXE>
On 26.1.2016 8:38, Joonsoo Kim wrote:
> On Mon, Jan 25, 2016 at 03:37:06PM -0800, Laura Abbott wrote:
>>
>> Is that series going to conflict with the work done for ZONE_DEVICE or run
>> into similar problems?
>> 033fbae988fcb67e5077203512181890848b8e90 (mm: ZONE_DEVICE for "device memory")
>> has commit text about running out of ZONE_SHIFT bits and needing to get
>> rid of ZONE_DMA instead so it seems like ZONE_CMA would run into the same
>> problem.
>
> Hmm... I'm not sure. I need a investigation. What I did before is
> enlarging section size. Then, number of section is reduced and we need
> less section bit in struct page's flag. This worked for my sparsemem
> configuration but I'm not sure other conguration. Perhaps, in other
> congifuration, we can limit node bits and max number of node.
This seems to be a solution proposed for the ZONE_DMA and ZONE_DEVICE
coexistence https://lkml.org/lkml/2016/1/25/1233
It wouldn't help with ZONE_CMA, so I guess it's time to look for a more robust one.
> Thanks.
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-01-26 18:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 4:41 Aneesh Kumar K.V
2016-01-22 9:17 ` Balbir Singh
2016-01-22 14:19 ` [Lsf-pc] " Jan Kara
2016-01-22 18:18 ` Laura Abbott
2016-01-27 19:07 ` Vlastimil Babka
2016-01-28 9:33 ` Aneesh Kumar K.V
2016-01-22 16:38 ` Johannes Weiner
2016-01-25 7:08 ` Joonsoo Kim
2016-01-25 23:37 ` Laura Abbott
2016-01-26 7:38 ` Joonsoo Kim
2016-01-26 18:53 ` Vlastimil Babka [this message]
2016-01-28 9:43 ` Aneesh Kumar K.V
2016-01-27 18:32 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2016-01-12 16:05 LSF/MM 2016: Call for Proposals Martin K. Petersen
2016-01-15 8:10 ` [LSF/MM ATTEND] 2016: Requests to attend MM-summit Jesper Dangaard Brouer
2016-01-15 16:49 ` Christoph Lameter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56A7C0B9.7040701@suse.cz \
--to=vbabka@suse.cz \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=labbott@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox