All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: William Lee Irwin III <wli@holomorphy.com>,
	Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: Re: clean up SLAB_KERNEL non-usage
Date: Sat, 15 Feb 2003 16:48:24 +0000	[thread overview]
Message-ID: <20030215164824.C21238@infradead.org> (raw)
In-Reply-To: <20030215120324.GG29983@holomorphy.com>; from wli@holomorphy.com on Sat, Feb 15, 2003 at 04:03:24AM -0800

On Sat, Feb 15, 2003 at 04:03:24AM -0800, William Lee Irwin III wrote:
> On Sat, Feb 15, 2003 at 03:40:54AM -0800, William Lee Irwin III wrote:
> >> Use SLAB_KERNEL and SLAB_ATOMIC instead of GFP_KERNEL and GFP_ATOMIC
> >> when passing args to slab allocation functions.
> 
> On Sat, Feb 15, 2003 at 11:49:31AM +0000, Christoph Hellwig wrote:
> > Why?  I'd prefer to completly get rid of the SLAB_ flags instead.
> > (stupid slowaris compat..)
> 
> IMHO different API, different flags. The inverse is not that difficult
> to produce, though.

I don't think this make much sense - kmalloc is a a different interface to
the same slab code and uses GFP_ flags, and __alloc_pages uses it aswell.


  reply	other threads:[~2003-02-15 16:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-15 11:40 clean up SLAB_KERNEL non-usage William Lee Irwin III
2003-02-15 11:49 ` Christoph Hellwig
2003-02-15 12:03   ` William Lee Irwin III
2003-02-15 16:48     ` Christoph Hellwig [this message]
2003-02-15 12:34   ` William Lee Irwin III
2003-02-15 12:42   ` William Lee Irwin III
2003-02-15 13:42   ` William Lee Irwin III
2003-02-15 13:45   ` William Lee Irwin III
2003-02-15 15:58 ` Oliver Neukum
2003-02-16  1:44   ` William Lee Irwin III

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=20030215164824.C21238@infradead.org \
    --to=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wli@holomorphy.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.