All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
To: "Chauhan, Vijay" <Vijay.Chauhan@lsi.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>
Subject: Re: [RFC PATCH 1/2] dm-mpath: interface change for	preparation
Date: Fri, 30 Jan 2009 17:06:21 +0900	[thread overview]
Message-ID: <4982B4FD.3070103@ct.jp.nec.com> (raw)
In-Reply-To: <0D1E8821739E724A86F4D16902CE275C13FF9B0272@inbmail01.lsi.com>

Hi Vijay,

Thank you for the comment.

On 01/30/2009 01:42 PM +0900, Chauhan, Vijay wrote:
> Hi Kiyoshi/Alasdair,
> 
> Just a thought. As we are changing __choose_pgpath parameters
> in this patch, will it be good to use BIO rather than nr_bytes
> as parameter? Availability of BIO in loadbalancing interface can
> provide more flexibility for coming up with new load balancing
> in future.

I understand that very much.
But I'd like to keep independency of path-selector from the type
of I/O structure as much as possible, since both bio-based targets
and request-based targets may want to use the same path-selector
in the future.  (e.g. multipath, which is requset-based,
and mirror, which is bio-based.)

So if we need only a few arguments, non-structured parameters
would be good, I think.
Do you have any idea what other parameters in BIO are useful for
load balancing decision?

Thanks,
Kiyoshi Ueda

  reply	other threads:[~2009-01-30  8:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  7:07 [RFC PATCH 0/0] dm-mpath: service-time oriented dynamic load balancer Kiyoshi Ueda
2009-01-29  7:10 ` [RFC PATCH 1/2] dm-mpath: interface change for preparation Kiyoshi Ueda
2009-01-30  4:42   ` Chauhan, Vijay
2009-01-30  8:06     ` Kiyoshi Ueda [this message]
2009-01-29  7:12 ` [RFC PATCH 2/2] dm-mpath: add service-time oriented dynamic load balancer Kiyoshi Ueda

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=4982B4FD.3070103@ct.jp.nec.com \
    --to=k-ueda@ct.jp.nec.com \
    --cc=Vijay.Chauhan@lsi.com \
    --cc=agk@redhat.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.