Re: [PATCH v4 1/4] mm: cma: introduce gfp flag in cma_alloc instead of no_warn

2021-01-27 Thread Minchan Kim
On Tue, Jan 26, 2021 at 11:12:14AM -0800, Minchan Kim wrote: > On Tue, Jan 26, 2021 at 08:38:08AM +0100, Michal Hocko wrote: > > On Mon 25-01-21 11:42:34, Minchan Kim wrote: > > > On Mon, Jan 25, 2021 at 02:07:01PM +0100, Michal Hocko wrote: > > > > On Thu 21-01-21 09:54:59, Minchan Kim wrote: > >

Re: [PATCH v4 1/4] mm: cma: introduce gfp flag in cma_alloc instead of no_warn

2021-01-26 Thread Minchan Kim
On Tue, Jan 26, 2021 at 08:38:08AM +0100, Michal Hocko wrote: > On Mon 25-01-21 11:42:34, Minchan Kim wrote: > > On Mon, Jan 25, 2021 at 02:07:01PM +0100, Michal Hocko wrote: > > > On Thu 21-01-21 09:54:59, Minchan Kim wrote: > > > > The upcoming patch will introduce __GFP_NORETRY semantic > > > >

Re: [PATCH v4 1/4] mm: cma: introduce gfp flag in cma_alloc instead of no_warn

2021-01-26 Thread Michal Hocko
On Mon 25-01-21 11:42:34, Minchan Kim wrote: > On Mon, Jan 25, 2021 at 02:07:01PM +0100, Michal Hocko wrote: > > On Thu 21-01-21 09:54:59, Minchan Kim wrote: > > > The upcoming patch will introduce __GFP_NORETRY semantic > > > in alloc_contig_range which is a failfast mode of the API. > > >

Re: [PATCH v4 1/4] mm: cma: introduce gfp flag in cma_alloc instead of no_warn

2021-01-25 Thread Michal Hocko
On Thu 21-01-21 09:54:59, Minchan Kim wrote: > The upcoming patch will introduce __GFP_NORETRY semantic > in alloc_contig_range which is a failfast mode of the API. > Instead of adding a additional parameter for gfp, replace > no_warn with gfp flag. > > To keep old behaviors, it follows the rule

Re: [PATCH v4 1/4] mm: cma: introduce gfp flag in cma_alloc instead of no_warn

2021-01-25 Thread Minchan Kim
On Mon, Jan 25, 2021 at 02:07:01PM +0100, Michal Hocko wrote: > On Thu 21-01-21 09:54:59, Minchan Kim wrote: > > The upcoming patch will introduce __GFP_NORETRY semantic > > in alloc_contig_range which is a failfast mode of the API. > > Instead of adding a additional parameter for gfp, replace > >

Re: [PATCH v4 1/4] mm: cma: introduce gfp flag in cma_alloc instead of no_warn

2021-01-21 Thread David Hildenbrand
On 21.01.21 18:54, Minchan Kim wrote: > The upcoming patch will introduce __GFP_NORETRY semantic > in alloc_contig_range which is a failfast mode of the API. > Instead of adding a additional parameter for gfp, replace > no_warn with gfp flag. > > To keep old behaviors, it follows the rule below.

Re: [PATCH v4 1/4] mm: cma: introduce gfp flag in cma_alloc instead of no_warn

2021-01-21 Thread Minchan Kim
On Thu, Jan 21, 2021 at 09:54:59AM -0800, Minchan Kim wrote: > The upcoming patch will introduce __GFP_NORETRY semantic > in alloc_contig_range which is a failfast mode of the API. > Instead of adding a additional parameter for gfp, replace > no_warn with gfp flag. > > To keep old behaviors, it

[PATCH v4 1/4] mm: cma: introduce gfp flag in cma_alloc instead of no_warn

2021-01-21 Thread Minchan Kim
The upcoming patch will introduce __GFP_NORETRY semantic in alloc_contig_range which is a failfast mode of the API. Instead of adding a additional parameter for gfp, replace no_warn with gfp flag. To keep old behaviors, it follows the rule below. no_warn gfp_flags