From: Lee Revell <rlrevell@joe-job.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.14-rt22 (and mainline): netstat -anop triggers excessive latencies
Date: Wed, 21 Dec 2005 18:19:45 -0500 [thread overview]
Message-ID: <1135207186.31433.15.camel@mindpipe> (raw)
In-Reply-To: <1135204629.14810.43.camel@localhost.localdomain>
On Wed, 2005-12-21 at 17:37 -0500, Steven Rostedt wrote:
> So it really does improve the latency here. Now is this worth the
> overhead? This might be useful in other places to.
Thanks, I'll try this.
But, AFAICT CONFIG_PREEMPT_SOFTIRQS is a much smaller patch... ;-)
Lee
next prev parent reply other threads:[~2005-12-21 23:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 6:04 2.6.14-rt22 (and mainline): netstat -anop triggers excessive latencies Lee Revell
2005-12-21 22:37 ` Steven Rostedt
2005-12-21 23:19 ` Lee Revell [this message]
2005-12-28 1:21 ` Lee Revell
2005-12-28 2:11 ` Steven Rostedt
2005-12-28 2:22 ` Lee Revell
2005-12-28 2:30 ` Steven Rostedt
2005-12-28 17:33 ` Lee Revell
2005-12-28 19:16 ` Steven Rostedt
2005-12-28 19:24 ` Steven Rostedt
2005-12-28 19:58 ` Lee Revell
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=1135207186.31433.15.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.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