mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Pekka J Enberg <penberg@cs.Helsinki.FI>
Cc: linux-kernel@vger.kernel.org, xfs-masters@oss.sgi.com
Subject: Re: [xfs-masters] Re: [PATCH] xfs: kill kmem_zone init
Date: Wed, 22 Mar 2006 08:55:20 +1100	[thread overview]
Message-ID: <20060322085520.A664708@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0603210859450.14023@sbz-30.cs.Helsinki.FI>; from penberg@cs.Helsinki.FI on Tue, Mar 21, 2006 at 09:05:14AM +0200

Hi Pekka,

On Tue, Mar 21, 2006 at 09:05:14AM +0200, Pekka J Enberg wrote:
> On Tue, 21 Mar 2006, Nathan Scott wrote:
> > Sorry, but thats just silly.  Did you even look at the code
> > around what you're changing (it has to do more than just wrap
> > up slab calls)?  So, NACK on this patch - it leaves the code
> > very confused (half zoney, half slaby), and is just unhelpful
> > code churn at the end of the day.
> 
> You're already using kmem_cache_destroy() mixed with the zone stuff so I 
> don't see your point.

Hmm, those ones have slipped through - I'll fix those up, thanks.
The vast majority of zone alloc/free uses are via the other style,
many variables are named according to those interfaces, etc, etc.

> I would really prefer to feed small bits at a time 
> so is there any way I can sweet-talk you into merging the patch?

Not without a very convincing argument, and "just kill wrappers
without even looking at the existing code" hasn't made me very
enthusiastic so far.

Regarding __GFP_NOFAIL, there are some situations where that could
be used now, and others where it should not be - it'd take a very
careful code audit and evidence of a level of low-memory-condition
testing done, etc, before such a change would be merged.  Note that
the -mm tree currently has a rework of the way incore extents are
managed within XFS, which significantly changes (in a good way) the
nature of the allocation requests we make (and hence I'm _really_,
_really_ not interested in cosmetic patches in this area just now).

cheers.

-- 
Nathan

  reply	other threads:[~2006-03-21 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-20 13:04 Pekka J Enberg
2006-03-20 21:20 ` Nathan Scott
2006-03-21  7:05   ` Pekka J Enberg
2006-03-21 21:55     ` Nathan Scott [this message]
2006-03-22  7:37       ` [xfs-masters] " Pekka J Enberg
2006-03-23  1:36         ` David Chinner

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=20060322085520.A664708@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.Helsinki.FI \
    --cc=xfs-masters@oss.sgi.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

all inboxes | Powered by JetHome®