From: Coly Li <colyli@suse.de>
To: Guoqing Jiang <guoqing.jiang@cloud.ionos.com>, songliubraving@fb.com
Cc: linux-raid@vger.kernel.org,
Kent Overstreet <kent.overstreet@gmail.com>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] raid5: use memalloc_noio_save()/restore in resize_chunks()
Date: Tue, 7 Apr 2020 23:09:21 +0800 [thread overview]
Message-ID: <5f27365b-768f-eb69-36ec-f4ed0c292c60@suse.de> (raw)
In-Reply-To: <fa7e30b9-7480-6c03-0f43-d561fed912fb@cloud.ionos.com>
On 2020/4/5 11:53 下午, Guoqing Jiang wrote:
> On 02.04.20 10:13, Coly Li wrote:
>> - scribble = kvmalloc_array(cnt, obj_size, flags);
>> + scribble = kvmalloc_array(cnt, obj_size, GFP_KERNEL);
>
> Maybe it is simpler to call kvmalloc_array between memalloc_noio_save
> and memalloc_noio_restore.
> And seems sched/mm.h need to be included per the report from LKP.
The falgs can be,
- GFP_KERNEL: when called from alloc_scratch_buffer()
- GFP_NOIO: when called from resize_chunks().
If the scope APIs are used inside scribble_alloc(), the first call path
is restricted as noio, which is not expected. So I only use the scope
APIs around the location where GFP_NOIO is used.
Anyway, Michal Hocko suggests to add the scope APIs in
mddev_suspend()/mddev_resume(). Then in the whole code path where md
raid array is suspend, we don't need to worry the recursive memory
reclaim I/Os onto the array. After checking the complicated raid5 code,
I come to realize this suggestion makes sense.
I will try to compose a v2 patch following Michal's suggestion.
--
Coly Li
next prev parent reply other threads:[~2020-04-07 15:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 8:13 [PATCH] raid5: use memalloc_noio_save()/restore in resize_chunks() Coly Li
2020-04-03 13:17 ` kbuild test robot
2020-04-05 15:53 ` Guoqing Jiang
2020-04-07 15:09 ` Coly Li [this message]
2020-04-09 21:38 ` Guoqing Jiang
2020-04-10 9:36 ` Coly Li
2020-04-15 11:48 ` Michal Hocko
2020-04-15 14:10 ` Guoqing Jiang
2020-04-15 14:23 ` Michal Hocko
2020-04-15 14:57 ` Guoqing Jiang
2020-04-30 6:36 ` Song Liu
2020-04-05 17:43 ` Song Liu
2020-04-07 14:42 ` Coly Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5f27365b-768f-eb69-36ec-f4ed0c292c60@suse.de \
--to=colyli@suse.de \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=songliubraving@fb.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox