From: David Miller <davem@davemloft.net>
To: chetanloke@gmail.com
Cc: shemminger@vyatta.com, Chetan.Loke@netscout.com,
bhutchings@solarflare.com, netdev@vger.kernel.org
Subject: Re: [RFC] Enhance dev_ioctl to return <hwaddr>:<if_name::if_index> mapping
Date: Fri, 16 Jul 2010 13:18:35 -0700 (PDT) [thread overview]
Message-ID: <20100716.131835.124042396.davem@davemloft.net> (raw)
In-Reply-To: <AANLkTineSDEEKY-9ve2maSBmPWBxkW5XmqnHlLtIOClx@mail.gmail.com>
From: Chetan Loke <chetanloke@gmail.com>
Date: Fri, 16 Jul 2010 16:15:44 -0400
> Ok, what if, i) ifindex == 0 in the call to SIOCGIFINDEX or ii) if the
> ifindex is not found ? May be then in the else clause we could search
> using the hw-addr before bailing out ;)? This way we can avoid adding
> a new API. Still not a good idea?
I'm really not going to consider this seriously, sorry. I've
made my position pretty clear, and gave sufficient reasons for
it.
Myself and others have also shown you several ways to fetch the
information you need, and of them netlink is probably the most
efficient, but the others work just as well.
The new interface proposals are just not a good idea.
next prev parent reply other threads:[~2010-07-16 20:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 13:18 [RFC] Enhance dev_ioctl to return <hwaddr>:<if_name::if_index> mapping Chetan Loke
2010-07-16 17:10 ` Ben Hutchings
2010-07-16 18:04 ` Stephen Hemminger
2010-07-16 18:12 ` Loke, Chetan
2010-07-16 18:31 ` Stephen Hemminger
2010-07-16 19:29 ` Chetan Loke
2010-07-16 19:33 ` David Miller
2010-07-16 19:35 ` Chetan Loke
2010-07-16 19:40 ` David Miller
2010-07-16 20:02 ` Chetan Loke
2010-07-16 20:04 ` David Miller
2010-07-16 20:15 ` Chetan Loke
2010-07-16 20:18 ` David Miller [this message]
2010-07-16 20:49 ` Loke, Chetan
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=20100716.131835.124042396.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Chetan.Loke@netscout.com \
--cc=bhutchings@solarflare.com \
--cc=chetanloke@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
/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).