netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: yoshfuji@linux-ipv6.org
Cc: rddunlap@osdl.org, linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC/PATCH] ICMPv6 MIB stats per-interface
Date: Mon, 14 Apr 2003 09:06:10 -0700 (PDT)	[thread overview]
Message-ID: <20030414.090610.117741299.davem@redhat.com> (raw)
In-Reply-To: <20030415.002915.71906095.yoshfuji@linux-ipv6.org>

   From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@linux-ipv6.org>
   Date: Tue, 15 Apr 2003 00:29:15 +0900 (JST)
   
   I'd recommend that we split information per interface
    1) to minimize the /proc file
    2) to minimize the effort to rewrite snmp daemon (e.g. net-snmp)
   We use /proc/net/dev_snmp6/{1,2,...}. Example:

I very much like this general idea.

But I want to suggest a different naming scheme.  Let us follow the
lead of things like /proc/sys/net/ipv4/conf/ where subfiles and
subdirectories are named using device name.

So we'd then have /proc/net/dev_snmp6/{lo,eth0,eth1} etc.

Ok?

  reply	other threads:[~2003-04-14 16:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-14 15:03 [RFC/PATCH] ICMPv6 MIB stats per-interface Randy.Dunlap
2003-04-14 15:29 ` YOSHIFUJI Hideaki / 吉藤英明
2003-04-14 16:06   ` David S. Miller [this message]
2003-04-14 16:40     ` YOSHIFUJI Hideaki / 吉藤英明
2003-04-14 16:35       ` David S. Miller
2003-04-14 16:50       ` Randy.Dunlap
2003-04-14 17:17         ` YOSHIFUJI Hideaki / 吉藤英明
2003-04-15 16:34           ` Randy.Dunlap
2003-04-15 18:07             ` YOSHIFUJI Hideaki / 吉藤英明
2003-04-15 18:12               ` Randy.Dunlap
2003-04-15  6:59       ` YOSHIFUJI Hideaki / 吉藤英明
2003-04-16 17:46         ` David S. Miller

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=20030414.090610.117741299.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=rddunlap@osdl.org \
    --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).