Thread (9 messages) flat view 9 messages, 5 authors, 2014-09-15

Re: [PATCHv4 0/3] new APIs to allocate buffer-cache with user specific flag

From: Theodore Ts'o <tytso@mit.edu>
Date: 2014-09-05 01:14:19
Also in: linux-fsdevel, lkml

On Fri, Sep 05, 2014 at 09:37:05AM +0900, Gioh Kim wrote:
quoted
But what were the problems which were observed in standard kernels and
what effect did this patchset have upon them?  Some quantitative
measurements will really help here.
The problem is that I cannot allocate entire CMA memory.
quoted
Actually the problem is not found without Joonsoo's patch:
https://lkml.org/lkml/2014/5/28/64.  Without it CMA memory is free
and every CMA-memory allocation is successed.

If the Joonsoo's patch is applied, the CMA memory is allocated
generally when system boots-up.
As I said earlier, I'm happy to carry this patch in the ext4 tree,
because as it turns out I could use this facility for another purpose
(to cause a few buffer cache allocations to happen with __GFP_NOFAIL).

I do have one question; I note that Joonsoo's patch dates back to May,
and yet this has not hit the mainline kernel, and I haven't seen any
discussions about this patch after May.  Has there been some pushback
from the mm maintainers about Joonsoo's approach with respect to this
patch?   What is the current status of that patch set?

Thanks,

					- Ted
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help