From: Krishna Kumar <krkumar@us.ibm.com>
To: "David S. Miller" <davem@redhat.com>
Cc: yoshfuji@linux-ipv6.org, kuznet@ms2.inr.ac.ru,
netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: [PATCH] Prefix List patch against 2.5.70
Date: Tue, 17 Jun 2003 13:46:01 -0700 [thread overview]
Message-ID: <3EEF7E09.8080608@us.ibm.com> (raw)
In-Reply-To: <20030530.233257.21920899.davem@redhat.com>
Hi Dave and Yoshfuji,
I have a question about the following, which seems to be the
approach both of you prefer. I thought we need a new routing
message type called RTM_GETPLIST which will return full prefix
list. If you use RTA_RA6INFO, then should that trigger only
when the prefix list has changed (add or delete) ? Should I
have both interfaces, one for returning entire list (RTM) and
one for changes in prefix list (RTA) ?
Please let me know if my understanding is correct.
Thanks,
- KK
David S. Miller wrote:
> From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
> Date: Sat, 31 May 2003 11:02:49 +0900 (JST)
>
> Again, what I proposed was to store prefix information on fib with
> some flags to represent advertised by routers and give user-space
> the RA information using new rtattr (RTA_RA6INFO or something like that).
>
> This sounds very reasonable.
>
next prev parent reply other threads:[~2003-06-17 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 1:15 [PATCH] Prefix List patch against 2.5.70 Krishna Kumar
2003-05-31 2:02 ` YOSHIFUJI Hideaki / 吉藤英明
2003-05-31 6:32 ` David S. Miller
2003-06-17 20:46 ` Krishna Kumar [this message]
2003-06-17 20:59 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-17 21:31 ` Krishna Kumar
2003-06-02 17:32 ` Krishna Kumar
2003-05-31 6:32 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2003-06-02 19:46 Krishna Kumar
2003-06-02 21:02 David Stevens
2003-06-03 4:48 ` Pekka Savola
2003-06-03 4:49 ` David S. Miller
2003-06-03 6:42 David Stevens
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=3EEF7E09.8080608@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 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).