From: Jens Axboe <axboe@suse.de>
To: "Philip R. Auld" <pauld@egenera.com>
Cc: Joe Thornber <thornber@redhat.com>,
dm-devel@sistina.com,
James Bottomley <James.Bottomley@steeleye.com>,
Simon Kelley <simon@thekelleys.org.uk>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [dm-devel] Re: Is there a grand plan for FC failover?
Date: Sat, 31 Jan 2004 18:42:01 +0100 [thread overview]
Message-ID: <20040131174201.GC11683@suse.de> (raw)
In-Reply-To: <20040131115903.A4881@vienna.EGENERA.COM>
On Sat, Jan 31 2004, Philip R. Auld wrote:
> Rumor has it that on Sat, Jan 31, 2004 at 10:30:37AM +0100 Jens Axboe said:
> > On Fri, Jan 30 2004, Joe Thornber wrote:
> > > It would be great to get some benchmarks to back up these arguments.
> > > eg, performance of dm mpath with a simple round robin selector,
> > > compared to a scsi layer implementation. Lifting the elevator (or
> > > lowering dm) is a big piece of work that I wont even consider unless
> > > there is very good reason; the reason probably needs to be broader
> > > than just multipath too. Even if we did decide to do this, it won't
> > > happen in 2.6.
> >
> > I suspect the problem really isn't that huge in 2.6, since most
> > performance file systems are using mpage or building their own big
> > bio's. So in a sense, some of the merging already does happen above dm
> > (and the io scheduler).
>
> Out of curiosity, where does raw io fit into that in 2.6?
raw io (or O_DIRECT io, same path) should work even better, always send
out bio's as big as the underlying device can support.
--
Jens Axboe
next prev parent reply other threads:[~2004-01-31 17:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 14:18 Is there a grand plan for FC failover? Simon Kelley
2004-01-26 15:37 ` James Bottomley
2004-01-28 15:02 ` Philip R. Auld
2004-01-28 16:57 ` James Bottomley
2004-01-28 18:00 ` Philip R. Auld
2004-01-28 20:47 ` Patrick Mansfield
2004-01-28 22:14 ` James Bottomley
2004-01-29 0:55 ` Patrick Mansfield
2004-01-30 19:48 ` [dm-devel] " Joe Thornber
2004-01-31 9:30 ` Jens Axboe
2004-01-31 16:59 ` Philip R. Auld
2004-01-31 17:42 ` Jens Axboe [this message]
2004-02-12 15:17 ` Philip R. Auld
2004-02-12 15:28 ` Arjan van de Ven
2004-02-12 16:03 ` Philip R. Auld
2004-01-28 22:37 ` Mike Christie
2004-01-29 15:24 ` Philip R. Auld
2004-01-29 16:00 ` James Bottomley
2004-01-29 23:25 ` Mike Christie
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=20040131174201.GC11683@suse.de \
--to=axboe@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=dm-devel@sistina.com \
--cc=linux-scsi@vger.kernel.org \
--cc=pauld@egenera.com \
--cc=simon@thekelleys.org.uk \
--cc=thornber@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox