From: Christoph Hellwig <hch@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.org, xfs@oss.sgi.com
Subject: Re: [patch 2/2] xfs: use scalable vmap API
Date: Mon, 1 Feb 2010 06:01:54 -0500 [thread overview]
Message-ID: <20100201110153.GA588@infradead.org> (raw)
In-Reply-To: <20100127083819.GA11072@laptop>
On Wed, Jan 27, 2010 at 07:38:19PM +1100, Nick Piggin wrote:
> > 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.
Still working fine, so please send it upstream ASAP. That'll make
re-eabling the scalable vmap API in XFS much more easier for 2.6.34.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
xfs@oss.sgi.com, linux-mm@kvack.org
Subject: Re: [patch 2/2] xfs: use scalable vmap API
Date: Mon, 1 Feb 2010 06:01:54 -0500 [thread overview]
Message-ID: <20100201110153.GA588@infradead.org> (raw)
In-Reply-To: <20100127083819.GA11072@laptop>
On Wed, Jan 27, 2010 at 07:38:19PM +1100, Nick Piggin wrote:
> > 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.
Still working fine, so please send it upstream ASAP. That'll make
re-eabling the scalable vmap API in XFS much more easier for 2.6.34.
--
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-02-01 11:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-21 8:25 [patch 1/2] xfs: remove old vmap cache Nick Piggin
2008-10-21 8:27 ` [patch 2/2] xfs: use scalable vmap API Nick Piggin
2008-10-21 12:09 ` Christoph Hellwig
2008-10-22 9:30 ` Nick Piggin
2010-01-19 12:15 ` Christoph Hellwig
2010-01-19 12:15 ` Christoph Hellwig
2010-01-25 7:54 ` Nick Piggin
2010-01-25 7:54 ` Nick Piggin
2010-01-25 8:17 ` Christoph Hellwig
2010-01-25 8:17 ` Christoph Hellwig
2010-01-25 8:33 ` Nick Piggin
2010-01-25 8:33 ` Nick Piggin
2010-01-25 12:37 ` Nick Piggin
2010-01-25 12:37 ` Nick Piggin
2010-01-25 12:39 ` Christoph Hellwig
2010-01-25 12:39 ` Christoph Hellwig
2010-01-25 21:34 ` Christoph Hellwig
2010-01-25 21:34 ` Christoph Hellwig
2010-01-27 8:38 ` Nick Piggin
2010-01-27 8:38 ` Nick Piggin
2010-02-01 11:01 ` Christoph Hellwig [this message]
2010-02-01 11:01 ` Christoph Hellwig
2010-02-01 11:28 ` Nick Piggin
2010-02-01 11:28 ` Nick Piggin
2010-01-25 8:30 ` Nick Piggin
2010-01-25 8:30 ` Nick Piggin
2008-10-21 12:09 ` [patch 1/2] xfs: remove old vmap cache Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2010-03-16 18:55 [PATCH 2/2] xfs: use scalable vmap API Alex Elder
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=20100201110153.GA588@infradead.org \
--to=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--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 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.