linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: add rules for new aoe character devices
Date: Mon, 10 Dec 2007 19:21:48 +0000	[thread overview]
Message-ID: <1197314508.6399.115.camel@lov.site> (raw)
In-Reply-To: <20071129171100.GF11161@coraid.com>

On Mon, 2007-12-10 at 10:34 -0500, Ed L. Cashin wrote:
> On Mon, Dec 03, 2007 at 07:42:58PM +0100, Kay Sievers wrote:
> > On Mon, 2007-12-03 at 13:38 -0500, Ed L. Cashin wrote:
> > > On Mon, Dec 03, 2007 at 07:15:03PM +0100, Kay Sievers wrote:
> ...
> > > > Does this rule work for you? It should move all nodes into a subdir:
> > > >   SUBSYSTEM="aoe",              NAME="etherd/%k"
> > > 
> > > Yes, that's good for the block devices.  In the past it seems that
> > > rule doesn't guarantee the creation of the character device nodes,
> > > though, and that is why there is a separate rule for each character
> > > node in the patch I sent.  I haven't checked yet whether the latest
> > > udev and kernel still behave the same way.
> > 
> > Block devices always have SUBSYSTEM="block", this will only handle the
> > char devices. You want the block devices to be in a subdir?
> 
> Yes, the normal arrangement is for the "etherd" subdirectory in /dev
> to contain the character and block devices for the aoe driver.  It
> looks like,
> 
>   ecashin@ellijay:~$ ls -l /dev/etherd 
>   total 0
>   c-w--w---- 1 root disk 152,  3 Dec  7 16:24 discover
>   brw-rw---- 1 root disk 152, 16 Dec  7 17:02 e7.0
>   brw-rw---- 1 root disk 152,  0 Dec  7 17:02 e7.1
>   cr--r----- 1 root disk 152,  2 Dec  7 16:24 err
>   c-w--w---- 1 root disk 152,  6 Dec  7 16:24 flush
>   c-w--w---- 1 root disk 152,  4 Dec  7 16:24 interfaces
>   c-w--w---- 1 root disk 152,  5 Dec  7 16:24 revalidate
>   ecashin@ellijay:~$ 
> 
> (The block device minor numbers are different for this aoe6-55 driver
> than they would be for earlier versions.  This aoe6-55 driver relies
> on udev and assigns minor numbers dynamically.  Older drivers can't do
> that, and so have a more limited range of possible AoE shelf and slot
> addresses.)

I see, the block device nodes have the "etherd/" prefix in the kernel,
so they don't need a udev rule to move them there. The name in sysfs has
a '!', like "/sys/block/etherd!e7.0/", right?

Kay


-------------------------------------------------------------------------
SF.Net email is sponsored by: 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2007-12-10 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 17:11 add rules for new aoe character devices Ed L. Cashin
2007-12-03 18:15 ` Kay Sievers
2007-12-03 18:38 ` Ed L. Cashin
2007-12-03 18:42 ` Kay Sievers
2007-12-03 18:52 ` Matthias Schwarzott
2007-12-10 15:34 ` Ed L. Cashin
2007-12-10 19:21 ` Kay Sievers [this message]
2007-12-10 20:07 ` Ed L. Cashin

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=1197314508.6399.115.camel@lov.site \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@vger.kernel.org \
    /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).