From: Christoph Hellwig <hch@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Christoph Hellwig <hch@infradead.org>,
lachlan@sgi.com, xfs-dev <xfs-dev@sgi.com>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] Tweak tracing allocation sizes
Date: Wed, 3 Sep 2008 08:06:35 -0400 [thread overview]
Message-ID: <20080903120635.GA14662@infradead.org> (raw)
In-Reply-To: <20080903070654.GP18288@one.firstfloor.org>
On Wed, Sep 03, 2008 at 09:06:54AM +0200, Andi Kleen wrote:
> On Tue, Sep 02, 2008 at 05:55:16PM -0400, Christoph Hellwig wrote:
> > On Tue, Sep 02, 2008 at 08:50:52AM +0200, Andi Kleen wrote:
> > > > alternative - maybe a very large global trace buffer that is allocated at mount
> > > > time and shared by all inodes?
> > >
> > > You could use vmalloc(). While that is also not fast it will at least
> > > not stall.
> >
> > In fact kmem_alloc first tries vmalloc, and then falls back to slab
> > when it fails. See fs/xfs/linux-2.6/kmem.c:kmem_alloc().
>
> You mean the other way around?
No, take a look at the function. I guess the intent is that vmalloc
can fail due to a full vmalloc area and kmalloc could theoretically
still scucceed.
prev parent reply other threads:[~2008-09-03 12:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 5:48 [PATCH] Tweak tracing allocation sizes Lachlan McIlroy
2008-09-02 5:56 ` Dave Chinner
2008-09-02 6:12 ` Lachlan McIlroy
2008-09-02 6:27 ` Dave Chinner
2008-09-02 21:54 ` Christoph Hellwig
2008-09-02 6:50 ` Andi Kleen
2008-09-02 21:55 ` Christoph Hellwig
2008-09-03 7:06 ` Andi Kleen
2008-09-03 12:06 ` Christoph Hellwig [this message]
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=20080903120635.GA14662@infradead.org \
--to=hch@infradead.org \
--cc=andi@firstfloor.org \
--cc=lachlan@sgi.com \
--cc=xfs-dev@sgi.com \
--cc=xfs@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