From: James Bottomley <James.Bottomley@SteelEye.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: itn780@yahoo.com, SCSI Mailing List <linux-scsi@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [ANNOUNCE 0/7] Open-iSCSI/Linux-iSCSI-5 High-Performance Initiator
Date: Sat, 30 Jul 2005 15:23:20 -0500 [thread overview]
Message-ID: <1122755000.5055.31.camel@mulgrave> (raw)
In-Reply-To: <20050730.125312.78734701.davem@davemloft.net>
On Sat, 2005-07-30 at 12:53 -0700, David S. Miller wrote:
> From: James Bottomley <James.Bottomley@SteelEye.com>
> Date: Sat, 30 Jul 2005 12:32:42 -0500
>
> > FIB has taken your netlink number, so I changed it to 32
>
> MAX_LINKS is 32, so there is no way this reassignment would
> work.
Actually, I saw this and increased MAX_LINKS as well. I was going to
query all of this on the net-dev mailing list if we'd managed to get the
code compileable.
> You have to pick something in the range 0 --> 32, and as is
> no surprise, there are no numbers available :-)
>
> Since ethertap has been deleted, 16-->31 could be made allocatable
> once more, but I simply do not want to do that and have the flood
> gates open up for folks allocating random netlink numbers.
>
> Instead, we need to take one of those netlink numbers, and turn
> it into a multiplexable layer that can support an arbitrary
> number of sub-netlink types. Said protocol would need some
> shim header that just says the "sub-netlink" protocol number,
> something as simple as just a "u32", this gets pulled off the
> front of the netlink packet and then it's passed on down to the
> real protocol.
I'll let the iSCSI people try this ...
Alternatively, if they don't fancy it, I think the kobject_uevent
mechanism (which already has a netlink number) looks like it might be
amenable for use for most of the things they want to do.
James
next prev parent reply other threads:[~2005-07-30 20:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 20:08 [ANNOUNCE 0/7] Open-iSCSI/Linux-iSCSI-5 High-Performance Initiator Alex Aizman
2005-06-01 20:54 ` Patrick McFarland
2005-06-01 21:08 ` Alex Aizman
2005-06-01 21:10 ` Ming Zhang
2005-07-30 17:32 ` James Bottomley
2005-07-30 18:36 ` Alex Aizman
2005-07-30 18:38 ` Christoph Hellwig
2005-07-30 19:53 ` David S. Miller
2005-07-30 19:53 ` David S. Miller
2005-07-30 20:23 ` James Bottomley [this message]
2005-07-30 21:25 ` Dmitry Yusupov
2005-07-31 0:33 ` David S. Miller
2005-08-02 17:18 ` Mike Christie
2005-07-31 0:34 ` David S. Miller
2005-08-06 20:46 ` Patrick McHardy
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=1122755000.5055.31.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=davem@davemloft.net \
--cc=hch@lst.de \
--cc=itn780@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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