From: Mike Christie <michaelc@cs.wisc.edu>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [ANNOUNCE] block layer (request based) multipath v1
Date: Thu, 20 Oct 2005 15:05:10 -0500 [thread overview]
Message-ID: <4357F876.80102@cs.wisc.edu> (raw)
In-Reply-To: <20051020135303.GD10778@free.fr>
Christophe Varoqui wrote:
> On Wed, Oct 19, 2005 at 01:20:44AM -0500, Mike Christie wrote:
>
>>Version 1 and maybe the only version :)
>>
>
> ...
>
>>I think the only items I have left to convert are some of the dm ioctls,
>>but that is trivial and the defaults are ok for usage. For example I
>>have not implemted a sysfs attr to read/write queue_if_no_path and a
>>timeout attr so we do not have to wait forever on it.
>>
>>Comments???? Should I work with Christophe to convert the userspace tools?
>>
>
> Nice,
>
> can libdevmapper event listening mecanisms be replaced by the uevents listener ?
> IOW, will all necessary attribute changes be reported as uevents ?
It looks like I am going to redo the patches and make it so dm call
request_fns. So we are basicall going to fix up dm-multipath instead of
making yet another multipath driver :)
>
> Events needed are :
> - multipath topology changes :
> - path add/remove (well, this one is guarantied through /block I guess)
> - attributes changes
> - path state changes / path reinstates
> - path group switches
> - multipath add/remove (Deduce from /block uevents ?)
>
I was just wondering where is all this netlink stuff? I have not seen a
dm-netlink interface patch. Are you just keying of events from the
kobject stuff?
next prev parent reply other threads:[~2005-10-20 20:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 6:20 [ANNOUNCE] block layer (request based) multipath v1 Mike Christie
2005-10-20 13:53 ` Christophe Varoqui
2005-10-20 20:05 ` Mike Christie [this message]
2005-10-20 20:08 ` Mike Christie
2005-10-20 20:08 ` Alasdair G Kergon
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=4357F876.80102@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--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.