Re: [RFC 0/2] Memoryless nodes and kworker
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Nish Aravamudan <nish.aravamudan@xxxxxxxxx>
- Subject: Re: [RFC 0/2] Memoryless nodes and kworker
- From: Tejun Heo <tj@xxxxxxxxxx>
- Date: Fri, 18 Jul 2014 14:01:10 -0400
- Cc: Nishanth Aravamudan <nacc@xxxxxxxxxxxxxxxxxx>, Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>, Joonsoo Kim <iamjoonsoo.kim@xxxxxxx>, David Rientjes <rientjes@xxxxxxxxxx>, Wanpeng Li <liwanp@xxxxxxxxxxxxxxxxxx>, Jiang Liu <jiang.liu@xxxxxxxxxxxxxxx>, Tony Luck <tony.luck@xxxxxxxxx>, Fenghua Yu <fenghua.yu@xxxxxxxxx>, linux-ia64@xxxxxxxxxxxxxxx, Linux Memory Management List <linux-mm@xxxxxxxxx>, linuxppc-dev@xxxxxxxxxxxxxxxx, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>
- In-reply-to: <20140718180008.GC13012@htj.dyndns.org>
- List-id: <linux-ia64.vger.kernel.org>
- References: <20140717230923.GA32660@linux.vnet.ibm.com> <20140718112039.GA8383@htj.dyndns.org> <CAOhV88PyBK3WxDjG1H0hUbRhRYzPOzV8eim5DuOcgObe-FtFYg@mail.gmail.com> <20140718180008.GC13012@htj.dyndns.org>
- User-agent: Mutt/1.5.23 (2014-03-12)
On Fri, Jul 18, 2014 at 02:00:08PM -0400, Tejun Heo wrote:
> This isn't a huge issue but it shows that this is the wrong layer to
> deal with this issue. Let the allocators express where they are.
^
allocator users
> Choosing and falling back belong to the memory allocator. That's the
> only place which has all the information that's necessary and those
> details must be contained there. Please don't leak it to memory
> allocator users.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]