linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Bellon <mbellon@mvista.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: ANNOUNCE: User-space System Device Enumation (uSDE)
Date: Mon, 27 Oct 2003 14:14:18 -0700	[thread overview]
Message-ID: <3F9D8AAA.7010308@mvista.com> (raw)
In-Reply-To: <20031027210054.GR24286@marowsky-bree.de>

>
>
>How does it relate to udev?
>
The uSDE and udev are simlar in some respects. The uSDE allows for 
complete control of the policy handling a device - not just its naming. 
It can perform complex policies on behalf of its devices including 
multiple concurrent policies for each device. It is also very aggressive 
about handing the system start up issues when many devices must be dealt 
with.

>How does this integrate with DM, md, EVMS, LVM...?
>
As devices appear in sysfs the uSDE reacts to them via their hotplug 
events. The policy for each device handles any device issues including 
dealing with any device nodes.  It is possible to track and maintain 
multiported devices and automatically provide multipath devices nodes 
for instance.

mark





  reply	other threads:[~2003-10-27 21:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27 20:41 ANNOUNCE: User-space System Device Enumation (uSDE) Mark Bellon
2003-10-27 21:00 ` Lars Marowsky-Bree
2003-10-27 21:14   ` Mark Bellon [this message]
2003-10-28 11:00     ` Lars Marowsky-Bree
2003-10-28 18:12       ` Steven Dake
2003-10-28 22:44         ` Greg KH
2003-10-27 23:15   ` Steven Dake
2003-10-27 23:19     ` Mark Bellon
  -- strict thread matches above, loose matches on Subject: below --
2003-10-29  5:12 Guo, Min
2003-10-29 16:10 ` Steven Dake
2003-10-29 19:04 ` Greg KH
2003-10-31  0:45 David Dodge
2003-10-31  0:58 ` Greg KH
2003-10-31  2:29   ` Dave Dodge

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=3F9D8AAA.7010308@mvista.com \
    --to=mbellon@mvista.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=lmb@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).