public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@redhat.com>
To: Mike Christie <mikenc@us.ibm.com>
Cc: Joe Thornber <thornber@redhat.com>, Andrew Morton <akpm@osdl.org>,
	Linux Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Patch 1/6] dm: endio method
Date: Mon, 23 Feb 2004 22:29:28 +0000	[thread overview]
Message-ID: <20040223222928.GB14731@reti> (raw)
In-Reply-To: <403A79E0.6080609@us.ibm.com>

On Mon, Feb 23, 2004 at 02:08:32PM -0800, Mike Christie wrote:
> With this move if the path has to be activated first, will the daemon 
> have to call some sort of ps_path_is_initialized() function before it 
> calls generic_make_request?

Yes, I am planning to add something like this.  Whether it needs to be
per path, or we could get away per priority group is probably a
question that you could answer better than me ?  Do we need a
corresponding deactivate for some hardware ?

> tio's map_info so it could be set from the daemon, or mp may need to 
> allocate its own io wrapper. It seems the latter may now be needed to 
> give ps's a a map_info, becuase dm-mpath needs to store the path in the 
> tio's map_info.

I think the bio recording/reset is going to have to move inside the
target.  It makes sense that the mpath target should be the only one
that incurs this overhead.  So yes, there will have to be a wrapper
which could be used to provide context for the ps.

- Joe

  reply	other threads:[~2004-02-23 22:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-20 15:31 device-mapper patchset Joe Thornber
2004-02-20 15:34 ` [Patch 1/6] dm: endio method Joe Thornber
2004-02-21  9:58   ` Mike Christie
2004-02-21 10:44     ` Christophe Saout
2004-02-23 10:05     ` Joe Thornber
2004-02-23 22:08       ` Mike Christie
2004-02-23 22:29         ` Joe Thornber [this message]
2004-02-24  2:18           ` Mike Christie
2004-02-20 15:34 ` [Patch 2/6] dm: remove v1 ioctl interface Joe Thornber
2004-02-20 20:18   ` Andreas Jellinghaus
2004-02-21  6:15   ` Andrew Morton
2004-02-20 15:35 ` [Patch 3/6] dm: list_for_each_entry audit Joe Thornber
2004-02-20 15:36 ` [Patch 4/6] dm: default queue limits Joe Thornber
2004-02-20 15:39   ` Joe Thornber
2004-02-20 15:37 ` [Patch 5/6] dm: list targets cmd Joe Thornber
2004-02-21  6:17   ` Andrew Morton
2004-02-20 15:37 ` [Patch 6/6] dm: multipath target Joe Thornber

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=20040223222928.GB14731@reti \
    --to=thornber@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikenc@us.ibm.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