From: "David S. Miller" <davem@redhat.com>
To: Shirley Ma <xma@us.ibm.com>
Cc: yoshfuji@linux-ipv6.org, mashirle@us.ibm.com,
kuznet@ms2.inr.ac.ru, netdev@oss.sgi.com
Subject: Re: [PATCH] IPv6 MIB:ipv6RouterAdvert netlink notification
Date: Fri, 16 Jan 2004 12:08:35 -0800 [thread overview]
Message-ID: <20040116120835.7f32f5e5.davem@redhat.com> (raw)
In-Reply-To: <OF6E7E4DFA.6824D151-ON87256E1D.006A89B5@us.ibm.com>
On Fri, 16 Jan 2004 11:41:59 -0800
Shirley Ma <xma@us.ibm.com> wrote:
> Does netlink support user-user communication?
Yes, it does.
One thing I want people to keep in mind in these discussions, while I understand
the concerns being addressed and discussed, I think it would be somewhat rediculious
for one to be required to go to multiple places just to put a complete ipv6 mib together.
For example, a bunch of procfs files, some netlink stuff, and some status files emitted
by some userlevel daemon. This is the situation I'd like to see avoided.
It looks like we can push all of this stuff over netlink, which would be ideal.
next prev parent reply other threads:[~2004-01-16 20:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 19:41 [PATCH] IPv6 MIB:ipv6RouterAdvert netlink notification Shirley Ma
2004-01-16 20:08 ` David S. Miller [this message]
2004-01-16 20:23 ` YOSHIFUJI Hideaki / 吉藤英明
-- strict thread matches above, loose matches on Subject: below --
2004-01-16 18:38 Shirley Ma
2004-01-16 19:17 ` YOSHIFUJI Hideaki / 吉藤英明
2004-01-15 22:31 Shirley Ma
2004-01-15 23:04 ` Shirley Ma
2004-01-15 23:04 ` David S. Miller
2004-01-16 1:37 ` YOSHIFUJI Hideaki / 吉藤英明
2003-11-20 0:21 IPv6 MIB:ipv6PrefixTable implementation Shirley Ma
2003-12-05 21:51 ` [PATCH] IPv6 MIB:ipv6Prefix netlink notification Shirley Ma
2003-12-05 22:57 ` David S. Miller
2004-01-14 23:52 ` [PATCH] IPv6 MIB:ipv6RouterAdvert " Shirley Ma
2004-01-15 8:52 ` David S. Miller
2004-01-15 9:10 ` 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=20040116120835.7f32f5e5.davem@redhat.com \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mashirle@us.ibm.com \
--cc=netdev@oss.sgi.com \
--cc=xma@us.ibm.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).