From: Eric Dumazet <dada1@cosmosbay.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Denys <nuclearcat@nuclearcat.com>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.21 -> 2.6.22 & 2.6.23-rc8 performance regression
Date: Mon, 01 Oct 2007 10:35:02 +0200 [thread overview]
Message-ID: <4700B136.8050109@cosmosbay.com> (raw)
In-Reply-To: <4700ADB7.7050102@cosmosbay.com>
Eric Dumazet a écrit :
> Denys a écrit :
>> Well, i can play a bit more on "live" servers. I have now hot-swap
>> server with
>> full gentoo, where i can rebuild any kernel you want, with any
>> applied patch.
>> But it looks more like not overhead, load becoming high too "spiky",
>> and it is
>> not just permantenly higher. Also it is not normal that all system
>> becoming
>> unresposive (for example ping 127.0.0.1 becoming 300ms for period,
>> when usage
>> softirq jumps to 100%).
>>
>>
> Could you try a pristine 2.6.22.9 and some patch in
> secure_tcp_sequence_number() like :
>
> --- drivers/char/random.c.orig 2007-10-01 10:18:42.000000000 +0200
> +++ drivers/char/random.c 2007-10-01 10:19:58.000000000 +0200
> @@ -1554,7 +1554,7 @@
> * That's funny, Linux has one built in! Use it!
> * (Networks are faster now - should this be increased?)
> */
> - seq += ktime_get_real().tv64;
> + seq += ktime_get_real().tv64 / 1000;
> #if 0
> printk("init_seq(%lx, %lx, %d, %d) = %d\n",
> saddr, daddr, sport, dport, seq);
On 32 bits machine, replace the divide by a shift to avoid a linker
error (undefined reference to `__divdi3'):
seq += ktime_get_real().tv64 >> 10;
next prev parent reply other threads:[~2007-10-01 8:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 14:48 2.6.21 -> 2.6.22 & 2.6.23-rc8 performance regression Denys
2007-09-30 17:48 ` Eric Dumazet
2007-09-30 4:25 ` Nick Piggin
2007-09-30 22:04 ` Denys
2007-10-01 10:01 ` Andi Kleen
2007-10-01 10:30 ` Denys
2007-10-01 11:14 ` Andi Kleen
2007-10-01 11:52 ` Denys
2007-10-01 11:57 ` Andi Kleen
2007-10-01 12:04 ` Denys
2007-09-30 22:35 ` Denys
2007-10-01 5:59 ` Eric Dumazet
2007-10-01 7:12 ` David Miller
2007-10-01 8:07 ` Denys
2007-10-01 8:20 ` Eric Dumazet
2007-10-01 8:35 ` Eric Dumazet [this message]
2007-10-01 12:10 ` Denys
2007-10-01 13:26 ` Denys
2007-10-01 20:10 ` Eric Dumazet
2007-10-01 20:57 ` David Miller
2007-09-30 23:24 ` Denys
2007-10-01 6:43 ` Denys
2007-09-30 18:45 ` Denys
-- strict thread matches above, loose matches on Subject: below --
2007-09-30 15:22 Denys
2007-09-30 17:31 Denys
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=4700B136.8050109@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nuclearcat@nuclearcat.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