From: Manfred Spraul <manfred@dbl.q-ag.de>
To: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: [RFC] 0/5 rcu lock update
Date: Tue, 25 May 2004 07:35:19 +0200 [thread overview]
Message-ID: <200405250535.i4P5ZJo8017583@dbl.q-ag.de> (raw)
Hi,
I tried to tackle the rcu scalability problem that Jack Steiner
noticed:
I found three changes that reduce the cache line trashing with
rcu_ctrlblk:
- Use generation numbers instead of the rcu_cpu_mask bitmap for
polling in rcu_pending. (patch 1)
- Use a sequence lock to check if a new batch must be started. Right
now each cpu acquires the global spinlock and usually notices that
the batch is already running. (patch 2)
- Hide implementation details - only fields that are accessed by
rcu_pending need to be visible in <linux/rcupdate.h> (patch 3)
- Preparation for hierarchical bitmap : hide locking (patch 4)
- Add a hierarchical bitmap (patch 5)
The first three patches are IMHO steps in the right direction,
suitable for inclusion. The last two patches are proof of concept
changes.
--
Manfred
reply other threads:[~2004-05-25 5:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200405250535.i4P5ZJo8017583@dbl.q-ag.de \
--to=manfred@dbl.q-ag.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech@lists.sourceforge.net \
/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).