From: kuznet@ms2.inr.ac.ru
To: jt@hpl.hp.com
Cc: linux-kernel@vger.kernel.org, alan@lxorguk.ukuu.org.uk
Subject: Re: RFC : Wireless Netlink events
Date: Wed, 10 Oct 2001 21:49:52 +0400 (MSK DST) [thread overview]
Message-ID: <200110101749.VAA04827@ms2.inr.ac.ru> (raw)
In-Reply-To: <20011009184700.B16874@bougret.hpl.hp.com> from "Jean Tourrilhes" at Oct 9, 1 06:47:00 pm
Hello!
> o Is there a way to do a reverse of SIOCGIFINDEX ? If you have
> an interface index, how do you get its name ?
SIOCGIFNAME.
But this does not matter, applications using rtnetlink should
not use these ioctls. They have all the information from rtnetlink.
> o Should I put the full interface name in the event ? That
> would make events larger but help query the interface when receiving
> the event.
Never. They are known from context.
> o Any other comments ?
I am not sure that it is right and in right place. I would not create one
more message type for such... mmm... special case.
Probably, you could add a new attribute to RTM_*LINK sort of
IFLA_MISC and to send ifinfo messages.
But I see logical flaw: no way to _retrieve_ information about state
on demand. Hence no right application cannot rely only on these messages.
Hence you should go all the way and to allow to dump this and,
probably, to add statistics shown in /proc/net/wireless.
Alexey
next prev parent reply other threads:[~2001-10-10 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 1:47 Jean Tourrilhes
2001-10-10 2:19 ` Jean Tourrilhes
2001-10-10 17:49 ` kuznet [this message]
2001-10-10 18:14 ` Jean Tourrilhes
2001-10-10 18:48 ` kuznet
2001-10-11 0:26 ` Jean Tourrilhes
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=200110101749.VAA04827@ms2.inr.ac.ru \
--to=kuznet@ms2.inr.ac.ru \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jt@hpl.hp.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®