From: Nick Piggin <npiggin@suse.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com, linux-mm@kvack.org
Subject: Re: [patch 2/2] xfs: use scalable vmap API
Date: Wed, 27 Jan 2010 19:38:19 +1100 [thread overview]
Message-ID: <20100127083819.GA11072@laptop> (raw)
In-Reply-To: <20100125213403.GA1309@infradead.org>
On Mon, Jan 25, 2010 at 04:34:03PM -0500, Christoph Hellwig wrote:
> On Mon, Jan 25, 2010 at 11:37:46PM +1100, Nick Piggin wrote:
> > On Mon, Jan 25, 2010 at 07:33:09PM +1100, Nick Piggin wrote:
> > > > Any easy way to get them? Sorry, not uptodate on your new vmalloc
> > > > implementation anymore.
> > >
> > > Let me try writing a few (tested) patches here first that I can send you.
> >
> > Well is it easy to reproduce the vmap failure? Here is a better tested
> > patch if you can try it. It fixes a couple of bugs and does some purging
> > of fragmented blocks.
>
> So far I've not run out of vmalloc space yet with quite a few xfstests
> iterations and not encountered any other problems either.
>
> Thanks for looking into this!
OK thanks for testing. I'll send it upstream if you haven't had any
problems so far.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-01-27 8:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20081021082542.GA6974@wotan.suse.de>
[not found] ` <20081021082735.GB6974@wotan.suse.de>
[not found] ` <20081021120932.GB13348@infradead.org>
[not found] ` <20081022093018.GD4359@wotan.suse.de>
2010-01-19 12:15 ` [patch 2/2] xfs: use scalable vmap API Christoph Hellwig
2010-01-25 7:54 ` Nick Piggin
2010-01-25 8:17 ` Christoph Hellwig
2010-01-25 8:33 ` Nick Piggin
2010-01-25 12:37 ` Nick Piggin
2010-01-25 12:39 ` Christoph Hellwig
2010-01-25 21:34 ` Christoph Hellwig
2010-01-27 8:38 ` Nick Piggin [this message]
2010-02-01 11:01 ` Christoph Hellwig
2010-02-01 11:28 ` Nick Piggin
2010-01-25 8:30 ` Nick Piggin
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=20100127083819.GA11072@laptop \
--to=npiggin@suse.de \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).