All of lore.kernel.org
 help / color / mirror / Atom feed
From: Song Liu <song@kernel.org>
To: Coly Li <colyli@suse.de>
Cc: Song Liu <songliubraving@fb.com>,
	linux-raid <linux-raid@vger.kernel.org>,
	mhocko@suse.com, kent.overstreet@gmail.com,
	Guoqing Jiang <guoqing.jiang@cloud.ionos.com>
Subject: Re: [PATCH v2 0/4] improve memalloc scope APIs usage
Date: Wed, 29 Apr 2020 23:49:39 -0700	[thread overview]
Message-ID: <CAPhsuW5EBYxNu2fqDO_jPbSuiGyUF5qgUCSLJYPAr2b6VPSytQ@mail.gmail.com> (raw)
In-Reply-To: <20200409115258.19330-1-colyli@suse.de>

On Thu, Apr 9, 2020 at 4:53 AM <colyli@suse.de> wrote:
>
> From: Coly Li <colyli@suse.de>
>
> Hi folks,
>
> The motivation of this series is to fix the incorrect GFP_NOIO flag
> usage in drivers/md/raid5.c:resize_chunks(). I take the suggestion
> from Michal Hocko to use memalloc scope APIs in unified entry point
> mddev_suspend()/mddev_resume(). Also I get rid of the incorect GFP_NOIO
> usage for scribble_alloc(), and remove redundant memalloc scope APIs
> usage in mddev_create_serial_pool(), also as Song Liu suggested, update
> the code comments on the header of scribble_alloc().
>
> Thank you in advance for the review and comments.
>
> Coly Li

Applied to md-next. Thanks for the fix. And Thanks Michal and Guoqing
for great inputs.

Song

      parent reply	other threads:[~2020-04-30  6:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-09 11:52 [PATCH v2 0/4] improve memalloc scope APIs usage colyli
2020-04-09 11:52 ` [PATCH v2 1/4] md: use memalloc scope APIs in mddev_suspend()/mddev_resume() colyli
2020-04-09 11:52 ` [PATCH v2 2/4] raid5: remove gfp flags from scribble_alloc() colyli
2020-04-09 11:52 ` [PATCH v2 3/4] raid5: update code comment of scribble_alloc() colyli
2020-04-09 11:52 ` [PATCH v2 4/4] md: remove redundant memalloc scope API usage colyli
2020-04-09 11:55   ` Coly Li
2020-04-30  6:49 ` Song Liu [this message]

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=CAPhsuW5EBYxNu2fqDO_jPbSuiGyUF5qgUCSLJYPAr2b6VPSytQ@mail.gmail.com \
    --to=song@kernel.org \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.