From: David Ford <david+cert@blue-labs.org>
To: linux-kernel@vger.kernel.org
Subject: Re: RFC: per-socket statistics on received/dropped packets
Date: Mon, 10 Jun 2002 14:44:04 -0400 [thread overview]
Message-ID: <3D04F374.8090001@blue-labs.org> (raw)
In-Reply-To: <3D039D22.2010805@candelatech.com> <20020609.213440.04716391.davem@redhat.com> <5.1.0.14.2.20020610220015.040aff60@mira-sjcm-3.cisco.com> <20020610.051857.97850707.davem@redhat.com>
Would you (David) mind having a file in the kernel that has a
list/description of such patches and a URL to them? This is the kind of
patch I would like to know is available somewhere so I don't spent a
week looking for it when someone asks about it.
-d
> would you be willing to accept a patch that enables per-socket
> accounting with a CONFIG_ option?
>
>What is the point?
>
>If all the dists will enable it then everybody eats the overhead.
>If the dists don't enable it, how useful is it and what's so wrong
>with it being an external patch people just apply when they need to
>diagnose something like this?
>
next prev parent reply other threads:[~2002-06-10 18:44 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 19:37 RFC: per-socket statistics on received/dropped packets Chris Friesen
2002-06-07 3:21 ` David S. Miller
2002-06-07 15:34 ` Chris Friesen
2002-06-07 22:15 ` Ben Greear
2002-06-08 21:05 ` Mark Mielke
2002-06-08 23:04 ` David S. Miller
2002-06-09 0:13 ` Ben Greear
2002-06-09 0:51 ` David S. Miller
2002-06-09 18:23 ` Ben Greear
2002-06-10 4:34 ` David S. Miller
2002-06-10 5:55 ` Mark Mielke
2002-06-10 6:08 ` Ben Greear
2002-06-10 12:03 ` Lincoln Dale
2002-06-10 12:18 ` David S. Miller
2002-06-10 12:24 ` jamal
2002-06-10 13:57 ` Mark Mielke
2002-06-10 14:45 ` jamal
2002-06-10 14:56 ` jamal
2002-06-10 19:28 ` Chris Friesen
2002-06-10 18:44 ` David Ford [this message]
2002-06-10 18:50 ` Thunder from the hill
2002-06-10 19:02 ` David Ford
2002-06-11 22:41 ` Bill Davidsen
2002-06-12 3:41 ` David S. Miller
2002-06-12 3:57 ` Richard Guy Briggs
2002-06-12 5:20 ` Mark Mielke
2002-06-12 6:08 ` Pekka Savola
2002-06-12 6:26 ` Ben Greear
2002-06-12 6:32 ` Pekka Savola
2002-06-12 6:49 ` Ben Greear
2002-06-12 12:11 ` Horst von Brand
2002-06-12 12:28 ` Lincoln Dale
2002-06-12 12:33 ` jamal
2002-06-12 12:44 ` Lincoln Dale
2002-06-12 13:00 ` jamal
2002-06-12 14:53 ` Mark Mielke
2002-06-12 15:57 ` jamal
2002-06-12 17:00 ` Horst von Brand
2002-06-14 0:24 ` Lincoln Dale
2002-06-14 15:51 ` Stephen Hemminger
2002-06-14 18:09 ` Ben Greear
2002-06-12 14:52 ` john slee
2002-06-12 14:55 ` Mark Mielke
2002-06-13 2:52 ` Lincoln Dale
2002-06-13 19:53 ` Horst von Brand
2002-06-13 7:21 ` David Schwartz
2002-06-13 8:44 ` Lincoln Dale
2002-06-13 10:10 ` David Schwartz
2002-06-23 2:03 ` Alan Cox
2002-06-23 2:05 ` Lincoln Dale
2002-06-12 9:18 ` Sean Hunter
2002-06-09 14:47 ` Pekka Pietikäinen
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=3D04F374.8090001@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=linux-kernel@vger.kernel.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