From: Krishna Kumar <krkumar@us.ibm.com>
To: kuznet@ms2.inr.ac.ru
Cc: yoshfuji@linux-ipv6.org, davem@redhat.com, netdev@oss.sgi.com,
linux-net@vger.kernel.org
Subject: Re: [PATCH 1/4] Prefix List against 2.5.73
Date: Wed, 16 Jul 2003 17:06:07 -0700 [thread overview]
Message-ID: <3F15E86F.2030707@us.ibm.com> (raw)
In-Reply-To: <200307162341.DAA12466@dub.inr.ac.ru>
This is sort of what I had originally, so I should be able to change
it to do this quite easily. I didn't like the earlier suggestion of
using existing RTM_xxxLINK with RTM_xxxIFACE (since it was dev generic),
but having a new interface RTM_xxxIFACE sounds good to me.
Thanks,
- KK
kuznet@ms2.inr.ac.ru wrote:
> Hello!
>
>
>>My suggestion is:
>> - create L3 per-interface RTM, say, RTM_xxxIFACE.
>> - provide inet_device / inet6_dev things via this RTM.
>> e.g. per-interface statistics, flags etc.
>
>
> I agree for all 100%. I understand your attitude now.
>
> Alexey
>
next prev parent reply other threads:[~2003-07-17 0:06 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 22:35 [PATCH 1/4] Prefix List against 2.5.73 Krishna Kumar
2003-07-15 1:17 ` kuznet
2003-07-15 6:59 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-15 13:20 ` kuznet
2003-07-15 18:34 ` Krishna Kumar
2003-07-16 0:11 ` Krishna Kumar
2003-07-16 0:21 ` kuznet
2003-07-16 8:39 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-16 18:42 ` [PATCH 1/2] " Krishna Kumar
2003-07-16 18:49 ` Krishna Kumar
2003-07-16 18:50 ` [PATCH 2/2] Prefix List against 2.4.21 Krishna Kumar
2003-07-16 23:41 ` [PATCH 1/4] Prefix List against 2.5.73 kuznet
2003-07-17 0:06 ` Krishna Kumar [this message]
2003-07-17 0:38 ` kuznet
2003-07-17 21:12 ` [PATCH 1/2] Prefix List and O/M flags " Krishna Kumar
2003-07-17 22:06 ` [PATCH 2/2] Prefix List and O/M flags against 2.4.21 Krishna Kumar
2003-07-17 22:22 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-17 22:34 ` Krishna Kumar
2003-07-17 22:47 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-18 0:37 ` [PATCH 2/2] Prefix List and O/M flags against 2.5.73 Krishna Kumar
2003-07-19 6:47 ` David S. Miller
2003-07-19 7:33 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-21 0:49 ` kuznet
2003-07-21 12:17 ` David S. Miller
2003-07-21 17:16 ` Krishna Kumar
2003-07-21 1:55 ` [PATCH 2/2] Prefix List and O/M flags against 2.4.21 kuznet
2003-07-21 4:46 ` David S. Miller
2003-07-22 21:50 ` O/M flags against 2.6.0-test1 Krishna Kumar
2003-07-22 22:25 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-22 22:59 ` Krishna Kumar
2003-07-23 10:13 ` David S. Miller
2003-07-23 22:32 ` Krishna Kumar
2003-07-24 7:07 ` David S. Miller
2003-07-24 14:02 ` kuznet
2003-07-24 14:26 ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-24 14:43 ` kuznet
2003-07-25 0:14 ` Krishna Kumar
2003-07-25 13:22 ` David S. Miller
2003-07-30 0:33 ` Krishna Kumar
2003-07-31 5:02 ` David S. Miller
2003-07-31 20:33 ` Krishna Kumar
2003-08-04 23:57 ` David S. Miller
2003-09-05 18:26 ` Krishna Kumar
2003-09-12 2:25 ` David S. Miller
2003-09-12 22:36 ` Krishna Kumar
2003-09-12 22:45 ` O/M flags for 2.4.22 (was "Re: O/M flags against 2.6.0-test1") Krishna Kumar
2003-09-13 0:19 ` David S. Miller
2003-09-16 22:06 ` Krishna Kumar
2003-09-20 8:18 ` David S. Miller
2003-07-22 23:52 ` [PATCH] Prefix List against 2.4.21 Krishna Kumar
2003-07-23 10:02 ` David S. Miller
2003-07-17 21:53 ` [PATCH 1/4] Prefix List against 2.5.73 YOSHIFUJI Hideaki / 吉藤英明
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=3F15E86F.2030707@us.ibm.com \
--to=krkumar@us.ibm.com \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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.