From: Albert Cahalan <albert@users.sf.net>
To: "David S. Miller" <davem@redhat.com>
Cc: dada1 <dada1@cosmosbay.com>,
lm@bitmover.com, albert@users.sourceforge.net,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: /proc reliability & performance
Date: 17 Oct 2003 19:48:12 -0400 [thread overview]
Message-ID: <1066434492.15921.211.camel@cube> (raw)
In-Reply-To: <20031017021040.4964309a.davem@redhat.com>
On Fri, 2003-10-17 at 05:10, David S. Miller wrote:
> On Fri, 17 Oct 2003 10:01:53 +0200
> "dada1" <dada1@cosmosbay.com> wrote:
>
> > A "cat /proc/net/tcp" takes too much time to even try it. :(
> >
> > tools like "netstat" or "lsof", (even with -n flag) are just unusable.
>
> Because they don't use the netlink TCP socket dumping
> facility which is made to handle such things much better
> than procfs ever can.
That's an accepted way to do things? Oh cool.
We just need a netlink process info dumping
facility...
next prev parent reply other threads:[~2003-10-18 0:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 2:07 /proc reliability & performance Albert Cahalan
2003-10-17 2:34 ` Larry McVoy
2003-10-17 8:01 ` dada1
2003-10-17 9:10 ` David S. Miller
2003-10-17 14:46 ` Valdis.Kletnieks
2003-10-17 17:24 ` dada1
2003-10-17 23:48 ` Albert Cahalan [this message]
2003-10-18 6:35 ` Willy Tarreau
2003-10-18 6:38 ` David S. Miller
2003-10-17 2:51 ` William Lee Irwin III
2003-10-17 3:24 ` Brian McGroarty
2003-10-17 4:31 ` Albert Cahalan
2003-10-17 4:56 ` William Lee Irwin III
2003-10-17 8:21 ` David Rees
2003-10-17 7:40 ` Zan Lynx
2003-10-17 7:54 ` William Lee Irwin III
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=1066434492.15921.211.camel@cube \
--to=albert@users.sf.net \
--cc=albert@users.sourceforge.net \
--cc=dada1@cosmosbay.com \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.