Re: [PATCH 7/9] md: use kvmalloc rather than opencoded variant

2017-02-01 Thread Michal Hocko
On Wed 01-02-17 12:29:56, Mikulas Patocka wrote: > > > On Mon, 30 Jan 2017, Michal Hocko wrote: > > > From: Michal Hocko > > > > copy_params uses kmalloc with vmalloc fallback. We already have a helper > > for that - kvmalloc. This caller requires GFP_NOIO semantic so it hasn't > > been conver

Re: [PATCH 7/9] md: use kvmalloc rather than opencoded variant

2017-02-01 Thread Mikulas Patocka
On Mon, 30 Jan 2017, Michal Hocko wrote: > From: Michal Hocko > > copy_params uses kmalloc with vmalloc fallback. We already have a helper > for that - kvmalloc. This caller requires GFP_NOIO semantic so it hasn't > been converted with many others by previous patches. All we need to > achieve

Re: [PATCH 7/9] md: use kvmalloc rather than opencoded variant

2017-01-30 Thread Vlastimil Babka
On 01/30/2017 10:49 AM, Michal Hocko wrote: From: Michal Hocko copy_params uses kmalloc with vmalloc fallback. We already have a helper for that - kvmalloc. This caller requires GFP_NOIO semantic so it hasn't been converted with many others by previous patches. All we need to achieve this seman

[PATCH 7/9] md: use kvmalloc rather than opencoded variant

2017-01-30 Thread Michal Hocko
From: Michal Hocko copy_params uses kmalloc with vmalloc fallback. We already have a helper for that - kvmalloc. This caller requires GFP_NOIO semantic so it hasn't been converted with many others by previous patches. All we need to achieve this semantic is to use the scope memalloc_noio_{save,re