From: Jens Axboe <jens.axboe@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com, sfr@canb.auug.org.au,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [bug?] bio: add experimental support for inlining a number of bio_vecs inside the bio
Date: Thu, 11 Dec 2008 08:32:28 +0100 [thread overview]
Message-ID: <20081211073226.GW23742@kernel.dk> (raw)
In-Reply-To: <20081210131311.e03d6fc5.akpm@linux-foundation.org>
On Wed, Dec 10 2008, Andrew Morton wrote:
> On Wed, 10 Dec 2008 13:12:38 +0100
> Jens Axboe <jens.axboe@oracle.com> wrote:
>
> > > experimental??
> >
> > Experimental in the sense that it's the first version, not the concept.
> > It's held up well for me, but just yesterday I received the first bug
> > report on a ppc platform and now you have this on ia64.
>
>
> Well there's another bug report up-list. "next-20081209: pdflush: page
> allocation failure (xfs)".
>
> The clearing of (__GFP_WAIT | __GFP_IO) will call the page allocator in the
> weakest possible mode and will of course spew page allocations warnings
> with great frequency. It should at least add in __GFP_NOWARN.
OK, that must be for the change titled
"bio: only mempool back the largest bio_vec slab cache"
and yes, that does look like it wants a bit more gfp loving, probably
the same as mempool_alloc() would use anyway. I'll get that fixed.
--
Jens Axboe
next prev parent reply other threads:[~2008-12-11 7:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-10 5:46 linux-next: Tree for December 10 Stephen Rothwell
2008-12-10 9:36 ` KOSAKI Motohiro
2008-12-10 12:05 ` [bug?] bio: add experimental support for inlining a number of bio_vecs inside the bio KOSAKI Motohiro
2008-12-10 12:12 ` Jens Axboe
2008-12-10 21:13 ` Andrew Morton
2008-12-11 7:32 ` Jens Axboe [this message]
2008-12-11 0:39 ` KOSAKI Motohiro
2008-12-10 9:39 ` linux-next: Tree for December 10 KOSAKI Motohiro
2008-12-10 11:21 ` KOSAKI Motohiro
2008-12-10 11:17 ` [BUILD-FAILURE] linux-next: next-20081210 - s390x - lcs drivers breaks with !CONFIG_IP_MULTICAST Kamalesh Babulal
2008-12-10 12:08 ` Heiko Carstens
2008-12-10 16:31 ` Kamalesh Babulal
2008-12-10 22:52 ` linux-next: Tree for December 10 Andrew Morton
2008-12-10 23:53 ` Rafael J. Wysocki
2008-12-11 0:38 ` Andrew Morton
2008-12-11 1:15 ` mpt fusion device warning 5 times KOSAKI Motohiro
2008-12-11 1:58 ` [PATCH] cpumask:cpumask_of_node-ia64 fix KOSAKI Motohiro
2008-12-11 4:09 ` [linux-next][PATCH] " KOSAKI Motohiro
2008-12-11 4:15 ` [PATCH] " Mike Travis
2008-12-11 4:31 ` Mike Travis
2008-12-11 4:53 ` KOSAKI Motohiro
2008-12-12 8:11 ` Rusty Russell
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=20081211073226.GW23742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).