netdev
[Top] [All Lists]

Re: [PATCH 2/2] Prefix List and O/M flags against 2.4.21

To: YOSHIFUJI Hideaki <yoshfuji@xxxxxxxxxxxxxx>
Subject: Re: [PATCH 2/2] Prefix List and O/M flags against 2.4.21
From: Krishna Kumar <krkumar@xxxxxxxxxx>
Date: Thu, 17 Jul 2003 15:34:05 -0700
Cc: krkumar@xxxxxxxxxx, kuznet@xxxxxxxxxxxxx, davem@xxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx
In-reply-to: <20030718.002209.104303756.yoshfuji@xxxxxxxxxxxxxx>
Organization: IBM
References: <Pine.LNX.4.44.0307171336430.1353-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.44.0307171413100.1353-100000@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030718.002209.104303756.yoshfuji@xxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130
Hmm, you seems still misunderstanding some of our points. :-p
Alexey says we may want to use ifi_family for per-interface L3 information
including M/O bits.

It is not a misunderstanding, I had replied to that mail saying that I don't
have any knowledge of using this new interface. If you prefer, I can split the
patch for prefix list vs O/M bits so that the former is accepted without any
issues. Someone else can modify the O/M to suit new needs. Does that sound OK
with you ?

> At least, new RTM_xxx should not be restricted to get such flags.

That's why I had suggested that we can use RTM_GETLNKINFO with more information,
like RTA_IFFLAGS, and other things like stats or whatever. That can be done
easily enough and still be functionally complete. I just don't have any idea
about this new interface.

Is this still a problem ?

thanks,

- KK


<Prev in Thread] Current Thread [Next in Thread>