On Fri 22-06-18 11:15:40, Davidlohr Bueso wrote:
> As of ce91f6ee5b3 (mm: kvmalloc does not fallback to vmalloc for incompatible
> gfp flag),
> we can simplify the caller and trust kvzalloc() to just do the right thing.
> For the
> case of the GFP_ATOMIC context, we can drop the __GFP_NORETRY
On Fri 22-06-18 11:15:40, Davidlohr Bueso wrote:
> As of ce91f6ee5b3 (mm: kvmalloc does not fallback to vmalloc for incompatible
> gfp flag),
> we can simplify the caller and trust kvzalloc() to just do the right thing.
> For the
> case of the GFP_ATOMIC context, we can drop the __GFP_NORETRY
On Fri, 22 Jun 2018, Davidlohr Bueso wrote:
This slightly changes the gfp flags passed on to nested_table_alloc() as it
will now
also use GFP_ATOMIC | __GFP_NOWARN. However, I consider this a positive
consequence
as for the same reasons we want nowarn semantics in bucket_table_alloc().
If
On Fri, 22 Jun 2018, Davidlohr Bueso wrote:
This slightly changes the gfp flags passed on to nested_table_alloc() as it
will now
also use GFP_ATOMIC | __GFP_NOWARN. However, I consider this a positive
consequence
as for the same reasons we want nowarn semantics in bucket_table_alloc().
If
Cc'ing Neil.
On Fri, 22 Jun 2018, Davidlohr Bueso wrote:
As of ce91f6ee5b3 (mm: kvmalloc does not fallback to vmalloc for incompatible
gfp flag),
we can simplify the caller and trust kvzalloc() to just do the right thing. For
the
case of the GFP_ATOMIC context, we can drop the __GFP_NORETRY
Cc'ing Neil.
On Fri, 22 Jun 2018, Davidlohr Bueso wrote:
As of ce91f6ee5b3 (mm: kvmalloc does not fallback to vmalloc for incompatible
gfp flag),
we can simplify the caller and trust kvzalloc() to just do the right thing. For
the
case of the GFP_ATOMIC context, we can drop the __GFP_NORETRY
As of ce91f6ee5b3 (mm: kvmalloc does not fallback to vmalloc for incompatible
gfp flag),
we can simplify the caller and trust kvzalloc() to just do the right thing. For
the
case of the GFP_ATOMIC context, we can drop the __GFP_NORETRY flag for obvious
reasons,
and for the __GFP_NOWARN case,
As of ce91f6ee5b3 (mm: kvmalloc does not fallback to vmalloc for incompatible
gfp flag),
we can simplify the caller and trust kvzalloc() to just do the right thing. For
the
case of the GFP_ATOMIC context, we can drop the __GFP_NORETRY flag for obvious
reasons,
and for the __GFP_NOWARN case,
8 matches
Mail list logo