public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: jacliburn@bellsouth.net, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] commit 3c517a61, slab: better fallback allocation behavior
Date: Tue, 12 Dec 2006 10:57:17 -0800	[thread overview]
Message-ID: <20061212105717.f539fb73.pj@sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0612110930180.500@schroedinger.engr.sgi.com>

Christoph wrote:
> +		if (local_flags & __GFP_WAIT)
> +			local_irq_enable();
> +		kmem_flagcheck(cache, flags);
>  		obj = kmem_getpages(cache, flags, -1);
> +		if (local_flags & __GFP_WAIT)
> +			local_irq_disable();

This seems strange to me.  I am surprised that it is ok for a routine
that is called with irq's disabled, to enable them momentarilly.

I'd have thought the caller of this routine, who called it with irq's
disabled, would expect irq's to remain disabled across the entire call.

I guess I'm assuming that disabled irq's are like a lock, not to be
momentarilly dropped by some nested routine without the explicit
awareness and consent of the caller.

But I don't really know what I'm talking about here.  Perhaps some
more clueful soul can educate me.

-- 
                  I won't rest till it's the best ...
                  Programmer, Linux Scalability
                  Paul Jackson <pj@sgi.com> 1.925.600.0401

  parent reply	other threads:[~2006-12-12 18:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-10 19:49 [BUG] commit 3c517a61, slab: better fallback allocation behavior Jay Cliburn
2006-12-10 20:49 ` Paul Jackson
2006-12-10 22:14   ` Andrew Morton
2006-12-11 17:13     ` Christoph Lameter
2006-12-11 17:37       ` Christoph Lameter
2006-12-11 19:41         ` Jay Cliburn
2006-12-12 18:57         ` Paul Jackson [this message]
2006-12-12 19:22           ` Christoph Lameter

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=20061212105717.f539fb73.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=jacliburn@bellsouth.net \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox