[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120529021558.GG20954@dhcp-172-17-108-109.mtv.corp.google.com>
Date: Tue, 29 May 2012 11:15:58 +0900
From: Tejun Heo <tj@...nel.org>
To: Dave Chinner <david@...morbit.com>
Cc: Mikulas Patocka <mpatocka@...hat.com>,
Alasdair G Kergon <agk@...hat.com>,
Kent Overstreet <koverstreet@...gle.com>,
Mike Snitzer <snitzer@...hat.com>,
linux-kernel@...r.kernel.org, linux-bcache@...r.kernel.org,
dm-devel@...hat.com, linux-fsdevel@...r.kernel.org,
axboe@...nel.dk, yehuda@...newdream.net, vgoyal@...hat.com,
bharrosh@...asas.com, sage@...dream.net, drbd-dev@...ts.linbit.com,
Dave Chinner <dchinner@...hat.com>, tytso@...gle.com,
"Martin K. Petersen" <martin.petersen@...cle.com>
Subject: Re: [PATCH v3 14/16] Gut bio_add_page()
Hello,
On Tue, May 29, 2012 at 12:08:15PM +1000, Dave Chinner wrote:
> > i thought a bit more about it and the only thing which makes sense to
> > me is exposing the stripe granularity for striped devices -
> > ie. something which says "if you go across this boundary, the
> > performance characteristics including latency might get affected",
> > which should fit nicely with the rest of topology information.
> > Martin, adding that shouldn't be difficult, right?
>
> We already have the optimal IO size/alignment field in the topology.
> Doesn't this fit what you want exactly?
I don't know how xfs/ext4 is currently benefiting from
merge_bvec_fn(), so I'm unsure. If the existing ones are enough,
great.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists