[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <D3F292ADF945FB49B35E96C94C2061B90C55C32A@nsmail.netscout.com>
Date: Fri, 16 Jul 2010 16:49:05 -0400
From: "Loke, Chetan" <Chetan.Loke@...scout.com>
To: "David Miller" <davem@...emloft.net>
Cc: <shemminger@...tta.com>, <bhutchings@...arflare.com>,
<netdev@...r.kernel.org>
Subject: RE: [RFC] Enhance dev_ioctl to return <hwaddr>:<if_name::if_index> mapping
Ooops... I got the 'CC' list this time
On Fri, Jul 16, 2010 at 4:33 PM, David Miller <davem@...emloft.net>
wrote:
> From: Chetan Loke <chetanloke@...il.com>
> Date: Fri, 16 Jul 2010 16:24:16 -0400
>
>> Thanks for your time guys.
>
> You dropped everything from the CC: list, so nobody other
> than me saw this. :)
>
>
On Fri, Jul 16, 2010 at 4:24 PM, Chetan Loke <chetanloke@...il.com>
wrote:
> On Fri, Jul 16, 2010 at 4:18 PM, David Miller <davem@...emloft.net>
wrote:
>> From: Chetan Loke <chetanloke@...il.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.
>>
>
> No problem Dave. I will patch our internal iso and add dev_getbyhwaddr
> in the else clause.
>
> Thanks for your time guys.
>
> regards
> Chetan Loke
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists