From: Roland Dreier <roland@topspin.com>
To: ak@muc.de, kuznet@ms2.inr.ac.ru
Cc: linux-kernel@vger.kernel.org, davem@redhat.com
Subject: rtnetlink replacement for SIOCSIFHWADDR
Date: 04 Dec 2002 10:31:14 -0800 [thread overview]
Message-ID: <52wumpbpql.fsf@topspin.com> (raw)
Hi, since you are the architects of the rtnetlink facility, I am
writing to you to ask your opinion on how to add some functionality.
I'm exploring what changes are needed in the kernel to support devices
with large addr_len. My motivation is to get the infrastructure for
IP-over-InfiniBand, which has addr_len 20, into the kernel, and I am
trying to produce a patch that can be accepted into mainline 2.5.
With a few a minor fixes to avoid overrunning array bounds, almost
everything just works. The RTM_NEWNEIGH and RTM_DELNEIGH messages
seem to provide what is needed to manage ARP entries with large L2
addresses (replacing the SIOCSARP and SIOCDARP ioctls).
The one major piece that is missing is a replacement for SIOCSIFHWADDR
(which can only set L2 addresses up to 14 bytes long, because of the
size of sa_data in struct sockaddr). I can see two ways one might set
an interface's L2 address through rtnetlink:
We could extend the RTM_NEWLINK message (possibly using the change
mask) to include changing just the L2 address, and add support in
the kernel for receiving these messages from userspace.
Or, we could add a new RTM_SETLINK message that userspace can send
to the kernel to modify an interface's properties.
Of course I am open to other suggestions for how to replace
SIOCSIFHWADDR. I would very much appreciate your thoughts on how to
proceed.
Thanks,
Roland <roland@topspin.com>
next prev reply other threads:[~2002-12-04 18:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 18:25 [PATCH] flush_cache_page while pte valid Hugh Dickins
2002-11-11 18:35 ` Andrew Morton
2002-11-11 23:19 ` David S. Miller
2002-11-11 23:34 ` [PATCH] [RFC] increase MAX_ADDR_LEN Roland Dreier
2002-11-11 23:38 ` David S. Miller
2002-11-11 23:58 ` Roland Dreier
2002-11-12 0:18 ` Alan Cox
2002-11-12 0:01 ` Roland Dreier
2002-11-12 14:23 ` Alan Cox
2002-11-12 14:20 ` Folkert van Heusden
2002-11-12 15:14 ` Roland Dreier
2002-11-12 16:00 ` Alan Cox
2002-11-12 15:50 ` YOSHIFUJI Hideaki / 吉藤英明
2002-11-12 20:36 ` Roland Dreier
2002-11-12 22:31 ` David S. Miller
2002-11-12 22:39 ` Roland Dreier
2002-12-04 18:31 ` Roland Dreier [this message]
2002-12-04 20:11 ` rtnetlink replacement for SIOCSIFHWADDR Andi Kleen
2002-12-31 23:11 ` [PATCH] increase MAX_ADDR_LEN Roland Dreier
2003-01-06 15:52 ` [PATCH] increase MAX_ADDR_LEN (resend) Roland Dreier
2003-01-06 23:29 ` David S. Miller
2003-01-07 8:58 ` [PATCH] increase MAX_ADDR_LEN David S. Miller
2002-11-12 6:53 ` [PATCH] flush_cache_page while pte valid Hugh Dickins
2002-11-12 6:53 ` David S. Miller
2002-11-12 14:49 ` Rik van Riel
2002-11-12 21:45 ` David S. Miller
2002-11-12 17:43 ` Hugh Dickins
2002-11-12 21:51 ` David S. Miller
2002-11-12 22:59 ` Hugh Dickins
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=52wumpbpql.fsf@topspin.com \
--to=roland@topspin.com \
--cc=ak@muc.de \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@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 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.