From: Nick Piggin <npiggin@suse.de>
To: Glauber Costa <glommer@redhat.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
torvalds@linux-foundation.org
Subject: Re: [patch 0/7] vmalloc fixes and improvements #2
Date: Wed, 12 Nov 2008 04:45:04 +0100 [thread overview]
Message-ID: <20081112034504.GE26053@wotan.suse.de> (raw)
In-Reply-To: <20081111182523.GB20481@poweredge.glommer>
On Tue, Nov 11, 2008 at 04:25:23PM -0200, Glauber Costa wrote:
> On Tue, Nov 11, 2008 at 12:35:15AM +1100, npiggin@suse.de wrote:
> > Hopefully got attribution right.
> >
> > Patches 1-3 fix "[Bug #11903] regression: vmalloc easily fail", and these
> > should go upstream for 2.6.28. They've been tested and shown to fix the
> > problem, and I've tested them here on my XFS stress test as well. The
> > off-by-one bug, I tested and verified in a userspace test harness (it
> > doesn't actually cause any corruption, but just suboptimal use of space).
> >
> > Patches 4,5 are improvements to information exported to user. Not very risky,
> > but not urgent either.
> >
> > Patches 6,7 improve locking and debugging modes a bit. I have not included
> > the changes to guard pages this time. They need a bit more explanation and
> > code review to justify. And probably some more philosophical discussions on
> > the mm list...
> >
> > --
>
> ok, news on this one inclusion?
Just waiting on Andrew. It won't get lost :)
--
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>
prev parent reply other threads:[~2008-11-12 3:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 13:35 npiggin
2008-11-10 13:35 ` [patch 1/7] mm: vmalloc allocator off by one npiggin, Nick Piggin
2008-11-10 13:35 ` [patch 2/7] mm: vmalloc failure flush fix npiggin, Nick Piggin
2008-11-10 13:35 ` [patch 3/7] mm: vmalloc search restart fix npiggin, Glauber Costa
2008-11-10 13:35 ` [patch 4/7] mm: vmalloc tweak failure printk npiggin, Glauber Costa
2008-11-10 13:35 ` [patch 5/7] mm: vmalloc improve vmallocinfo npiggin, Glauber Costa
2008-11-10 13:35 ` [patch 6/7] mm: vmalloc use mutex for purge npiggin, Nick Piggin
2008-11-10 13:35 ` [patch 7/7] mm: vmalloc make lazy unmapping configurable npiggin, Nick Piggin
2008-11-11 18:25 ` [patch 0/7] vmalloc fixes and improvements #2 Glauber Costa
2008-11-12 3:45 ` Nick Piggin [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=20081112034504.GE26053@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=glommer@redhat.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@linux-foundation.org \
/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