From: Dipankar Sarma <dipankar@in.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Matt Mackall <mpm@selenic.com>, linux-kernel@vger.kernel.org
Subject: [PATCH] reduce rcu_head size [0/2]
Date: Wed, 16 Jun 2004 11:16:04 +0530 [thread overview]
Message-ID: <20040616054604.GA3658@in.ibm.com> (raw)
This was originally proposed by Rusty. I have it in two patches
for a reason - rcu-no-arg changes the call_rcu() api and if it
is too late in 2.6 to introduce it, we could still do some
shrinking by applying the singly-linked-rcu patch. Other than
the documented changes, there is no subtle semantics change -
rcus are still invoked in the same order.
Andrew, this will probably break manfred's patches, but
512-cpu scalability can probably wait a little until
I get around to analyze those (my next task in hand) :)
I have tested the patches lightly on an x86 box.
Thanks
Dipankar
next reply other threads:[~2004-06-16 5:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 5:46 Dipankar Sarma [this message]
2004-06-16 5:47 ` [PATCH] reduce rcu_head size [1/2] Dipankar Sarma
2004-06-16 5:47 ` [PATCH] reduce rcu_head size [2/2] Dipankar Sarma
2004-06-19 19:04 ` Andrew Morton
2004-06-20 6:12 ` Dipankar Sarma
2004-06-22 17:50 ` Dipankar Sarma
2004-06-22 17:57 ` Andrew Morton
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=20040616054604.GA3658@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@osdl.org \
--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