All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy <genanr@emsphone.com>
To: dm-devel@redhat.com
Subject: multipath multibus performance
Date: Thu, 31 Jan 2008 10:39:18 -0600	[thread overview]
Message-ID: <20080131163918.GA10313@thumper2> (raw)

I would like to increase the performance of the multibus mode of multipath. 
It would be nice if multibus performance would be very close to accessing
the device directly.  From what I have been told, under multibus, I/O's are
broken up into bio's and sent down the multiple paths, with no merging of
adjacent I/O's.  Would it be possible to add code to the kernel so that
adjacent (at least some of them, probably make configurable) would be merged
and sent on a single path?  And, would this increase the performance of
multibus mode?  

I would be willing to work on it myself, but I have never done any kernel
coding (I done plenty of C coding) and would not know where to look to even
attempt adding I/O merging to multipath.

What do you think?  Would this work, and how would I go about doing it?

Andy

             reply	other threads:[~2008-01-31 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 16:39 Andy [this message]
2008-01-31 18:26 ` multipath multibus performance malahal

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=20080131163918.GA10313@thumper2 \
    --to=genanr@emsphone.com \
    --cc=dm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.