From: Andi Kleen <andi@firstfloor.org>
To: David Miller <davem@davemloft.net>
Cc: csnook@redhat.com, andi@firstfloor.org, rick.jones2@hp.com,
netdev@vger.kernel.org
Subject: Re: RFC: Nagle latency tuning
Date: Mon, 22 Sep 2008 22:30:42 +0200 [thread overview]
Message-ID: <20080922203042.GY25711@one.firstfloor.org> (raw)
In-Reply-To: <20080922.040912.193700258.davem@davemloft.net>
On Mon, Sep 22, 2008 at 04:09:12AM -0700, David Miller wrote:
> From: David Miller <davem@davemloft.net>
> Date: Mon, 22 Sep 2008 03:49:33 -0700 (PDT)
>
> > I'll try to figure out why Andi's patch doesn't behave as expected.
>
> Andi's patch uses proc_dointvec_jiffies, which is for sysctl values
> stored as seconds, whereas these things are used to record values with
> smaller granulatiry, are stored in jiffies, and that's why we get zero
> on read and writes have crazy effects.
Oops. Assume me with brown paper bag etc.etc.
It was a typo for proc_dointvec_ms_jiffies
>
> Also, as Andi stated, this is not the way to deal with this problem.
>
> So we have a broken patch, which even if implemented properly isn't the
> way forward, so I consider this discussion dead in the water until we
> have some test cases.
The patch is easy to fix with a s/_jiffies/_ms_jiffies/g
Also it was more intended for him to play around and get some data
points. I guess for that it's still useful.
Also while for that it's probably not the right solution, but
I could imagine in some other situations where it might be useful
to tune these values. After all they are not written down in stone.
I wonder if it would even make sense to consider hr timers for TCP
now.
=Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-09-22 20:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 21:56 RFC: Nagle latency tuning Christopher Snook
2008-09-08 22:39 ` Rick Jones
2008-09-09 5:10 ` Chris Snook
2008-09-09 5:17 ` David Miller
2008-09-09 5:56 ` Chris Snook
2008-09-09 6:02 ` David Miller
2008-09-09 10:31 ` Mark Brown
2008-09-09 12:05 ` David Miller
2008-09-09 12:09 ` Mark Brown
2008-09-09 12:19 ` David Miller
2008-09-09 6:22 ` Evgeniy Polyakov
2008-09-09 6:28 ` Chris Snook
2008-09-09 13:00 ` Arnaldo Carvalho de Melo
2008-09-09 14:36 ` Andi Kleen
2008-09-09 18:40 ` Chris Snook
2008-09-09 19:07 ` Andi Kleen
2008-09-09 19:21 ` Arnaldo Carvalho de Melo
2008-09-11 4:08 ` Chris Snook
2008-09-09 19:59 ` David Miller
2008-09-09 20:25 ` Chris Snook
2008-09-22 10:49 ` David Miller
2008-09-22 11:09 ` David Miller
2008-09-22 20:30 ` Andi Kleen [this message]
2008-09-22 22:22 ` Chris Snook
2008-09-22 22:26 ` David Miller
2008-09-22 23:00 ` Chris Snook
2008-09-22 23:13 ` David Miller
2008-09-22 23:24 ` Andi Kleen
2008-09-22 23:21 ` David Miller
2008-09-23 0:14 ` Andi Kleen
2008-09-23 0:33 ` Rick Jones
2008-09-23 2:12 ` Andi Kleen
2008-09-23 1:40 ` David Miller
2008-09-23 2:23 ` Andi Kleen
2008-09-23 2:28 ` David Miller
2008-09-23 2:41 ` Andi Kleen
2008-09-22 22:47 ` Rick Jones
2008-09-22 22:57 ` Chris Snook
2008-09-09 16:33 ` Rick Jones
2008-09-09 16:54 ` Chuck Lever
2008-09-09 17:21 ` Arnaldo Carvalho de Melo
2008-09-09 17:54 ` Rick Jones
2008-09-08 22:55 ` Andi Kleen
2008-09-09 5:22 ` Chris Snook
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=20080922203042.GY25711@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=csnook@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.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 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).