From: David Mosberger <davidm@napali.hpl.hp.com>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>,
davidm@hpl.hp.com, davidm@napali.hpl.hp.com,
linux-kernel@vger.kernel.org
Subject: Re: Fw: potential /dev/urandom scalability improvement
Date: Thu, 25 Mar 2004 20:51:54 -0800 [thread overview]
Message-ID: <16483.46826.466847.77987@napali.hpl.hp.com> (raw)
In-Reply-To: <20040326041926.GG8366@waste.org>
>>>>> On Thu, 25 Mar 2004 22:19:26 -0600, Matt Mackall <mpm@selenic.com> said:
> struct entropy_store {
> + /* mostly-read data: */
> + struct poolinfo poolinfo;
> + __u32 *pool;
> +
> + /* read-write data: */
> + spinlock_t lock ____cacheline_aligned;
> unsigned add_ptr;
> int entropy_count;
> int input_rotate;
> - struct poolinfo poolinfo;
> - __u32 *pool;
> - spinlock_t lock;
> };
Matt> Also, I think in general we'd prefer to stick the aligned bit at the
Matt> front of the structure rather than at the middle, as we'll avoid extra
Matt> padding. The size of cachelines is getting rather obscene on some
Matt> modern processors.
Not sharing the cacheline between the mostly-read data and the
read-write data is the _point_ of this change. If you reverse the
order, the "poolinfo" and "pool" members will also get invalidated
whenever someone updates the write-intensive data.
--david
next prev parent reply other threads:[~2004-03-26 4:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040325141923.7080c6f0.akpm@osdl.org>
2004-03-25 22:47 ` Matt Mackall
2004-03-26 1:45 ` David Mosberger
2004-03-26 2:00 ` Andrew Morton
2004-03-26 2:10 ` David Mosberger
2004-03-26 4:07 ` Matt Mackall
2004-03-26 4:19 ` Matt Mackall
2004-03-26 4:51 ` David Mosberger [this message]
2004-03-26 5:15 ` Matt Mackall
2004-03-26 5:24 ` David Mosberger
2004-03-26 11:06 ` Dave Jones
2004-03-26 18:08 ` David Mosberger
2004-03-26 18:23 ` Dave Jones
2004-03-26 21:31 ` David Mosberger
2004-03-26 18:49 ` Andrew Morton
2004-03-26 20:25 ` David Mosberger
2004-03-26 20:33 ` Andrew Morton
2004-03-26 20:45 ` Arjan van de Ven
2004-03-26 21:17 ` Andrew Morton
2004-03-27 7:44 ` Arjan van de Ven
2004-03-26 21:12 ` David Mosberger
[not found] <1DLZM-8aK-67@gated-at.bofh.it>
[not found] ` <1DLZM-8aK-65@gated-at.bofh.it>
[not found] ` <1DOE1-20o-17@gated-at.bofh.it>
[not found] ` <1DOXn-2k7-5@gated-at.bofh.it>
[not found] ` <1DXxI-Z7-39@gated-at.bofh.it>
[not found] ` <1E467-6KK-17@gated-at.bofh.it>
[not found] ` <1E4IT-7f3-21@gated-at.bofh.it>
2004-03-27 1:29 ` Andi Kleen
2004-03-27 15:48 ` Matt Mackall
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=16483.46826.466847.77987@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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
all inboxes | Powered by JetHome®