netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krishna Kumar <krkumar@us.ibm.com>
To: "YOSHIFUJI Hideaki" <yoshfuji@linux-ipv6.org>
Cc: "David S. Miller" <davem@redhat.com>,
	netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: [PATCH] Prefix List against 2.5.70 (re-done)
Date: Mon, 30 Jun 2003 11:54:41 -0700	[thread overview]
Message-ID: <3F008771.5030206@us.ibm.com> (raw)
In-Reply-To: <20030628.130602.63704890.yoshfuji@linux-ipv6.org>


> 1. is it okay to have another hook for garbbig prefix list?
>    Userspace application can get such information via
>    - routing table
>    - interface flag
> 
> 2. is the "managed" flags etc, which is per interface variable, 
>    really NEWROUTE information?
>    It is NOT L2 thing, but it is per-link information.
>    I think it is NEWLINK thing.
> 
> What I'm thinking is:
> 
>  - fix "ADDRCONF" flag in route information
>  - manage / other flags via NEWLINK message
> (- No new interface to get prefix itself.)


Well, there are two reason that I can see to not do so (ADDRCONF flag is already
fixed in earlier patch) :

-  With the latest submission, the actual code to get the prefix list itself
    is very small, the top level inet6_dump_fib uses either the dump_node or
    the dump_prefix, the latter being the new function added. This is the whole
    user interface, 50 odd lines of code with comments.
-  If I understood your point about using interface flag and routing table,
    you are suggesting that the user can make look at rttable and get the prefix
    entries by make checks (it is non-trivial, eg the address should not LL or MC,
    there should be no nexthop and it should be added via an RA, etc). However,
    having a user interface makes it easier to get the prefix list without
    significant bloat to the kernel, and the user doesn't have to make a lot of
    checks to get the system prefixes. I don't see much gain from this approach.

About your point about the managed flag, I think it is a per interface flag
that gets returned when a request for getting flags on that interface is made.
That's why I have made it per interface as part of a GETLNKFLAGS operation.
I don't understand why you think it is NEWLINK thing (not sure what you mean by
that), since it is a flag information on your existing device that a RA is
advertising. I want to get this information not on receipt of an RA, but when
a request is made.

Thanks,

- KK


  reply	other threads:[~2003-06-30 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-20 20:53 [PATCH] Prefix List against 2.5.70 (re-done) Krishna Kumar
2003-06-21 14:36 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-25 17:02   ` Krishna Kumar
2003-06-26  6:42     ` David S. Miller
2003-06-26 16:32       ` Krishna Kumar
2003-06-27  6:07         ` David S. Miller
2003-06-27 15:45           ` Krishna Kumar
2003-06-27 21:47             ` David S. Miller
2003-06-28  4:06               ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-30 18:54                 ` Krishna Kumar [this message]
2003-07-02  0:18                   ` YOSHIFUJI Hideaki / 吉藤英明
2003-07-10 22:16                     ` Krishna Kumar
2003-06-26 22:40       ` [PATCH] Prefix List against 2.4.21 Krishna Kumar

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=3F008771.5030206@us.ibm.com \
    --to=krkumar@us.ibm.com \
    --cc=davem@redhat.com \
    --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).