public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Tejun Heo <tj@kernel.org>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>,
	Kent Overstreet <koverstreet@google.com>,
	Mike Snitzer <snitzer@redhat.com>,
	linux-kernel@vger.kernel.org, linux-bcache@vger.kernel.org,
	dm-devel@redhat.com, linux-fsdevel@vger.kernel.org,
	axboe@kernel.dk, yehuda@hq.newdream.net, vgoyal@redhat.com,
	bharrosh@panasas.com, sage@newdream.net,
	drbd-dev@lists.linbit.com, Dave Chinner <dchinner@redhat.com>,
	tytso@google.com,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v3 14/16] Gut bio_add_page()
Date: Tue, 29 May 2012 12:08:15 +1000	[thread overview]
Message-ID: <20120529020815.GB5091@dastard> (raw)
In-Reply-To: <20120528230208.GA20954@dhcp-172-17-108-109.mtv.corp.google.com>

On Tue, May 29, 2012 at 08:02:08AM +0900, Tejun Heo wrote:
> (cc'ing Martin K. Petersen, hi!)
> 
> On Tue, May 29, 2012 at 06:38:39AM +0900, Tejun Heo wrote:
> > > With this patchset, you don't have to expose all the limits. You can 
> > > expose just a few most useful limits to avoid bio split in the cases 
> > > described above.
> > 
> > Yeah, if that actually helps, sure.  From what I read, dm is already
> > (ab)using merge_bvec_fn() like that anyway.
> 
> 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?

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2012-05-29  2:08 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-25 20:25 [PATCH v3 00/16] Block cleanups Kent Overstreet
2012-05-25 20:25 ` [PATCH v3 01/16] block: Generalized bio pool freeing Kent Overstreet
2012-05-28  1:15   ` Tejun Heo
2012-05-28 10:04   ` Boaz Harrosh
2012-05-25 20:25 ` [PATCH v3 02/16] dm: Use bioset's front_pad for dm_rq_clone_bio_info Kent Overstreet
2012-05-28  0:57   ` [dm-devel] " Jun'ichi Nomura
2012-05-28 11:41     ` Jun'ichi Nomura
2012-05-28  1:21   ` Tejun Heo
2012-05-25 20:25 ` [PATCH v3 03/16] block: Add bio_reset() Kent Overstreet
2012-05-28  1:23   ` Tejun Heo
2012-05-28 10:02     ` Boaz Harrosh
2012-05-25 20:25 ` [PATCH v3 04/16] pktcdvd: Switch to bio_kmalloc() Kent Overstreet
2012-05-28  1:30   ` Tejun Heo
2012-05-25 20:25 ` [PATCH v3 05/16] block: Kill bi_destructor Kent Overstreet
2012-05-28  1:36   ` Tejun Heo
2012-05-29  2:10     ` Kent Overstreet
2012-05-29  2:20       ` Tejun Heo
2012-05-25 20:25 ` [PATCH v3 06/16] block: Add an explicit bio flag for bios that own their bvec Kent Overstreet
2012-05-28  1:52   ` Tejun Heo
2012-05-25 20:25 ` [PATCH v3 07/16] block: Rename bio_split() -> bio_pair_split() Kent Overstreet
2012-05-28 10:15   ` Boaz Harrosh
2012-05-29  2:15     ` Kent Overstreet
2012-05-25 20:25 ` [PATCH v3 08/16] block: Rework bio splitting Kent Overstreet
2012-05-28 16:12   ` Mikulas Patocka
2012-05-25 20:25 ` [PATCH v3 09/16] block: Add bio_clone_kmalloc() Kent Overstreet
2012-05-25 20:25 ` [PATCH v3 10/16] block: Add bio_clone_bioset() Kent Overstreet
2012-05-25 20:25 ` [PATCH v3 11/16] block: Only clone bio vecs that are in use Kent Overstreet
2012-05-25 20:25 ` [PATCH v3 12/16] Closures Kent Overstreet
2012-05-25 20:57   ` Joe Perches
2012-05-25 21:35     ` Kent Overstreet
2012-05-25 20:25 ` [PATCH v3 13/16] Make generic_make_request handle arbitrarily large bios Kent Overstreet
2012-05-25 22:58   ` Alasdair G Kergon
2012-05-25 23:12     ` Alasdair G Kergon
2012-05-26  0:18       ` Kent Overstreet
2012-05-25 20:25 ` [PATCH v3 14/16] Gut bio_add_page() Kent Overstreet
2012-05-25 20:46   ` Mike Snitzer
2012-05-25 21:09     ` Kent Overstreet
2012-05-25 22:39       ` Alasdair G Kergon
2012-05-28 16:07         ` Mikulas Patocka
2012-05-28 20:28           ` Tejun Heo
2012-05-28 21:27             ` Mikulas Patocka
2012-05-28 21:38               ` Tejun Heo
2012-05-28 23:02                 ` Tejun Heo
2012-05-29  2:08                   ` Dave Chinner [this message]
2012-05-29  2:15                     ` Tejun Heo
2012-05-29  3:36                       ` Kent Overstreet
2012-05-29  2:07                 ` Dave Chinner
2012-05-29  1:54       ` Dave Chinner
2012-05-29  3:34         ` Kent Overstreet
2012-06-05  0:33           ` Dave Chinner
2012-05-25 20:25 ` [PATCH v3 15/16] md: Kill merge_bvec_fn()s Kent Overstreet
2012-05-25 20:25 ` [PATCH v3 16/16] dm: Kill merge_bvec_fn() Kent Overstreet

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=20120529020815.GB5091@dastard \
    --to=david@fromorbit.com \
    --cc=agk@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=bharrosh@panasas.com \
    --cc=dchinner@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=drbd-dev@lists.linbit.com \
    --cc=koverstreet@google.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mpatocka@redhat.com \
    --cc=sage@newdream.net \
    --cc=snitzer@redhat.com \
    --cc=tj@kernel.org \
    --cc=tytso@google.com \
    --cc=vgoyal@redhat.com \
    --cc=yehuda@hq.newdream.net \
    /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