From: Christophe Varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: dm-multipath [PATCH] multipathd adding devices.
Date: Thu, 2 Mar 2006 17:38:13 +0100 [thread overview]
Message-ID: <20060302163813.GF14155@pundit> (raw)
In-Reply-To: <C2EEB4E538D3DC48BF57F391F422779321B079@SRMANNING.eng.emc.com>
On Thu, Mar 02, 2006 at 11:28:04AM -0500, egoggin@emc.com wrote:
> On Thu, Mar 02, 2006 at 12:09:31PM +0100, Christophe Varoqui wrote:
> > > On Fri, Feb 24, 2006 at 08:33:29PM -0600, Benjamin Marzinski wrote:
> > > > The way multipathd currently works, if you add a map that
> > isn't known to
> > > > device mapper from multipathd, the first time you run the
> > command, it won't
> > > > add the map to the mpvec vector. With the attached
> > patch, multipathd will
> > > > initialize the map and add it to the mpvec vector.
> > > >
> > > How does the current behaviour affects you ?
> > > Is this about races between DM and netlink events ?
> > >
> > To be more specific, I think the current code rely on the
> > netlink "map add" event triggered by coalesce_paths() to feed
> > the mpvec asynchronously.
> >
> > ... which seems ok to me, but I may miss a point.
>
> What is the "current" code, the code in the git repository or
> the latest release point multipath-tools-0.4.6.1? This certainly
> works fine in the code from the git repository.
>
I was refering to the git HEAD.
Regards,
cvaroqui
next prev parent reply other threads:[~2006-03-02 16:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 16:28 dm-multipath [PATCH] multipathd adding devices egoggin
2006-03-02 16:38 ` Christophe Varoqui [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-25 2:33 Benjamin Marzinski
2006-03-02 11:09 ` Christophe Varoqui
2006-03-02 15:41 ` Christophe Varoqui
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=20060302163813.GF14155@pundit \
--to=christophe.varoqui@free.fr \
--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.