From: David Miller <davem@davemloft.net>
To: andi@firstfloor.org
Cc: netdev@vger.kernel.org
Subject: Re: [PING^3] [PATCH] srandom32 fixes for networking v2
Date: Thu, 03 Apr 2008 14:07:23 -0700 (PDT) [thread overview]
Message-ID: <20080403.140723.249778614.davem@davemloft.net> (raw)
In-Reply-To: <20080403203611.GA25305@basil.nowhere.org>
From: Andi Kleen <andi@firstfloor.org>
Date: Thu, 3 Apr 2008 22:36:11 +0200
> srandom32 fixes for networking v2
>
> - Let it update the state of all CPUs. The network stack goes
> into pains to feed the current IP addresses in, but it is not very
> effective if that is only done for some random CPU instead of all.
> So change it to feed bits into all CPUs. I decided to do that lockless
> because well somewhat random results are ok.
>
> v2: Drop rename so that this patch doesn't depend on x86 maintainers
>
> Signed-off-by: Andi Kleen <ak@suse.de>
Applied, thanks.
prev parent reply other threads:[~2008-04-03 21:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-03 20:36 [PING^3] [PATCH] srandom32 fixes for networking v2 Andi Kleen
2008-04-03 21:07 ` David Miller [this message]
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=20080403.140723.249778614.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andi@firstfloor.org \
--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).