From: Roland Dreier <rdreier@cisco.com>
To: Andi Kleen <ak@suse.de>
Cc: meissner@suse.de, netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH] [1/2] Skip empty hash buckets faster in /proc/net/tcp
Date: Wed, 30 Jan 2008 09:03:16 -0800 [thread overview]
Message-ID: <adasl0fb60b.fsf@cisco.com> (raw)
In-Reply-To: <20080130901.138686634@suse.de> (Andi Kleen's message of "Wed, 30 Jan 2008 09:01:09 +0100 (CET)")
> On a 2GB Core2 system here I see a time cat /proc/net/tcp > /dev/null
> constently dropping from 0.44s to 0.4-0.8s system time with this change.
Seems like there must be a typo in either the before or after times
you report here?
next prev parent reply other threads:[~2008-01-30 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 8:01 [PATCH] [1/2] Skip empty hash buckets faster in /proc/net/tcp Andi Kleen
2008-01-30 8:01 ` [PATCH] [2/2] Remove some unnecessary gotos in established_get_first() Andi Kleen
2008-01-30 8:25 ` Oliver Neukum
2008-01-30 8:27 ` Andi Kleen
2008-01-30 13:46 ` David Miller
2008-01-30 17:03 ` Roland Dreier [this message]
2008-01-30 17:32 ` [PATCH] [1/2] Skip empty hash buckets faster in /proc/net/tcp Andi Kleen
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=adasl0fb60b.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=ak@suse.de \
--cc=davem@davemloft.net \
--cc=meissner@suse.de \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).