public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <mikenc@us.ibm.com>
To: Joe Thornber <thornber@redhat.com>
Cc: 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 14:08:32 -0800	[thread overview]
Message-ID: <403A79E0.6080609@us.ibm.com> (raw)
In-Reply-To: <20040223100512.GB943@reti>

Hey Joe,

Joe Thornber wrote:

> Mike,
> 
> On Sat, Feb 21, 2004 at 01:58:38AM -0800, Mike Christie wrote:
> 
>>Saving and restoring bi_bdev is going to break multipath.
> 
> 
> Yes, we'll have to fall back to plan A and use the map_context pointer
> to hold the path being used (attached patch for illustration only).  I
> had been hoping we could keep the map_context unused so that we could
> allow the path selectors to use it.  I should have spotted this.
> 
> I'll also move the failed bio remap back to mpath_end_io(), so that
> the context can be reused there (it moved to the daemon when we were
> trying to do path testing in the kernel).
>

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?

It might be easier if mp's map_io call did not move so it or the ps 
could send commands and wait for the response before selecting a path. I 
guess this would mean you would have to add a access function for the 
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.

Mike

  reply	other threads:[~2004-02-23 22:15 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 [this message]
2004-02-23 22:29         ` Joe Thornber
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=403A79E0.6080609@us.ibm.com \
    --to=mikenc@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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