All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] Don't use unnecessary GFP_ATOMIC in sg.c
Date: Mon, 25 Feb 2008 15:56:25 +0100	[thread overview]
Message-ID: <20080225145625.GA16158@one.firstfloor.org> (raw)
In-Reply-To: <1203950588.3254.12.camel@localhost.localdomain>

On Mon, Feb 25, 2008 at 06:43:08AM -0800, James Bottomley wrote:
> On Mon, 2008-02-25 at 00:36 +0100, Andi Kleen wrote:
> > Don't use unnecessary GFP_ATOMIC in sg.c
> > 
> > sg.c uses GFP_ATOMIC for a lot of allocations where it isn't necessary.
> > There are no locks hold and I don't see any other reasons why GFP_ATOMIC
> > should be needed here. So remove them for more reliable allocations.
> > 
> > Depends on the earlier GFP_DMA patchkit, but only because it happens
> > to patch the same places (no real functional dependency) 
> > 
> > Tested by burning a CD on a kernel with all lock/sleep/etc. debugging enabled.
> 
> I'm afraid this is wrong.  Those paths are used in the block layer issue
> path.  Most of the time this path does have user context.  However, it's
> legal to call it from tasklet context, and most error retries do this.
> In that case, your GFP_KERNEL will have problems, so these have to be
> GFP_ATOMIC, I'm afraid.

In what path? I couldn't find one while reading the code. But I don't
claim to understand it completely so I might have missed something.

-Andi

  reply	other threads:[~2008-02-25 14:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 23:36 [PATCH] Don't use unnecessary GFP_ATOMIC in sg.c Andi Kleen
2008-02-25 14:43 ` James Bottomley
2008-02-25 14:56   ` Andi Kleen [this message]
2008-02-25 15:00     ` James Bottomley
2008-02-25 15:08       ` Andi Kleen

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=20080225145625.GA16158@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    /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.