From: Mike Snitzer <snitzer@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Chandra Seetharaman <chandra.seetharaman@us.ibm.com>,
"michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>,
Rob Evers <revers@redhat.com>,
Babu.Moger@lsi.com
Subject: Re: scsi_dh_rdac: Changing the memory allocation flag from GFP_KERNEL to GFP_NOIO
Date: Thu, 4 Nov 2010 11:14:37 -0400 [thread overview]
Message-ID: <20101104151436.GA1026@redhat.com> (raw)
In-Reply-To: <E463DF2B2E584B4A82673F53D62C2EF4877BC7E8@cosmail01.lsi.com>
This patch appears to have gotten lost in the shuffle but still seems
relevant. I found it while auditing dm-devel's patchwork, patch is
here: https://patchwork.kernel.org/patch/71073/
On Tue, Jan 05 2010 at 12:20pm -0500,
Moger, Babu <Babu.Moger@lsi.com> wrote:
> This patch changes the memory allocation flag from GFP_KERNEL to GFP_NOIO which is more appropriate.
>
> This was noticed by Mike Christie and Rob Evers..
> Mike Christie wrote:
> > Rob Evers wrote:
> >> +
> >> +static int queue_mode_select(struct scsi_device *sdev,
> >> + activate_complete fn, void *data)
> >> +{
> >> + struct rdac_queue_data *qdata;
> >> + struct rdac_controller *ctlr;
> >> +
> >> + qdata = kzalloc(sizeof(*qdata), GFP_KERNEL);
> >> + if (!qdata)
> >> + return SCSI_DH_RETRY;
> >> +
> >
> > It looks like this is called in the main IO path. A failed IO could cause, the path to go down,
> > then we would call this to active a new path. If the system needed to write out pages to the same
> > disk that just had the failed path so it can allocate memory then GFP_KERNEL would be bad to use here.
> > You would use a mempool and still use something like GFP_NOIO. If a mempool is not possible for some
> > reason, then you would want to still use GFP_NOIO.
>
> Using mempool would become bit more complex here because I cannot assume about the number of elements
> during the allocation. I would use GFP_NOIO.
>
> CC: Mike Christie <michaelc@cs.wisc.edu>
> CC: Rob Evers <revers@redhat.com>
> CC: Chandra Seetharaman <chandra.seetharaman@us.ibm.com>
> Signed-off-by: Babu Moger <babu.moger@lsi.com>
>
> ---
> --- linux-2.6.33-rc2/drivers/scsi/device_handler/scsi_dh_rdac.c.orig 2010-01-05 11:49:22.000000000 -0400
> +++ linux-2.6.33-rc2/drivers/scsi/device_handler/scsi_dh_rdac.c 2010-01-05 11:53:13.000000000 -0400
> @@ -624,7 +624,7 @@ static int queue_mode_select(struct scsi
> struct rdac_queue_data *qdata;
> struct rdac_controller *ctlr;
>
> - qdata = kzalloc(sizeof(*qdata), GFP_KERNEL);
> + qdata = kzalloc(sizeof(*qdata), GFP_NOIO);
> if (!qdata)
> return SCSI_DH_RETRY;
>
>
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2010-11-04 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 17:20 [PATCH] scsi_dh_rdac: Changing the memory allocation flag from GFP_KERNEL to GFP_NOIO Moger, Babu
2010-01-27 22:19 ` [dm-devel] " Chandra Seetharaman
2010-11-04 15:14 ` Mike Snitzer [this message]
2010-11-04 15:20 ` Moger, Babu
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=20101104151436.GA1026@redhat.com \
--to=snitzer@redhat.com \
--cc=Babu.Moger@lsi.com \
--cc=chandra.seetharaman@us.ibm.com \
--cc=dm-devel@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=revers@redhat.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;
as well as URLs for NNTP newsgroup(s).