From: "David S. Miller" <davem@redhat.com>
To: "YOSHIFUJI Hideaki / _$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: shep@alum.mit.edu, kuznet@ms2.inr.ac.ru, pekkas@netcore.fi,
jmorris@redhat.com, netdev@oss.sgi.com, torvalds@osdl.org,
linux-kernel@vger.kernel.org, yoshfuji@linux-ipv6.org
Subject: Re: [PATCH] fix numbering of lines in /proc/net/tcp (linux-2.6.0-test7)
Date: Tue, 14 Oct 2003 10:45:03 -0700 [thread overview]
Message-ID: <20031014104503.12ca907e.davem@redhat.com> (raw)
In-Reply-To: <20031015.013848.133364889.yoshfuji@linux-ipv6.org>
On Wed, 15 Oct 2003 01:38:48 +0900 (JST)
YOSHIFUJI Hideaki / _$B5HF#1QL@ <yoshfuji@linux-ipv6.org> wrote:
> In article <200310141619.h9EGJWWB013461@ginger.lcs.mit.edu> (at Tue, 14 Oct 2003 12:19:32 -0400), Tim Shepard <shep@alum.mit.edu> says:
>
> > I am not sure what the behavior is supposed to be. Is there a spec
> > anywhere for the interface with /proc/net/tcp?
>
> Yes, I think the original is okay because the bucket is shared between
> tcp6 and tcp4, and I don't want to change this behavior in 2.6 from 2.4.x.
> (so, we need to fix 2.6.x.)
In the meantime I've applied Tim's patch because it is definitely
a step in the right direction and the current 2.6.x behavior makes
no sense at all :-)
We can add a fix on top to make 2.6.x behave more closely to 2.4.x
(by sharing numbers between v4 and v6). If that proves to be very
difficult to do, it's not absolutely critical to preserve this behavior
I think.
next prev parent reply other threads:[~2003-10-14 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-14 16:19 [PATCH] fix numbering of lines in /proc/net/tcp (linux-2.6.0-test7) Tim Shepard
2003-10-14 16:38 ` YOSHIFUJI Hideaki / 吉藤英明
2003-10-14 17:45 ` David S. Miller [this message]
2003-10-14 18:14 ` Tim Shepard
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=20031014104503.12ca907e.davem@redhat.com \
--to=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
--cc=shep@alum.mit.edu \
--cc=torvalds@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).