From: Dipankar Sarma <dipankar@in.ibm.com>
To: "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: ak@suse.de, maneesh@in.ibm.com, shemminger@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] Improve readability by hiding read_barrier_depends() calls
Date: Fri, 6 Aug 2004 00:57:56 +0530 [thread overview]
Message-ID: <20040805192756.GE3935@in.ibm.com> (raw)
In-Reply-To: <20040804142845.GB1865@us.ibm.com>
On Wed, Aug 04, 2004 at 07:28:46AM -0700, Paul E. McKenney wrote:
> Hello!
>
> Updated based on feedback, and merged forward to 2.6.8-rc3.
>
> This patch introduced an rcu_dereference() macro that replaces most
> uses of smp_read_barrier_depends(). The new macro has the advantage
> of explicitly documenting which pointers are protected by RCU -- in
> contrast, it is sometimes difficult to figure out which pointer is
> being protected by a given smp_read_barrier_depends() call.
>
I have a series of 3 patches in my stack that applies on existing
3 RCU patches in -mm2 -
rcu-code-cleanup : Major cleanup removing per_cpu() calculations and use pointers to RCU global and per-cpu data.
call-rcu-bh : Introduce call_rcu_bh() for faster grace periods with
softirq-only code.
use-call-rcu-bh : use call_rcu_bh in ipv4 route cache. This helps avoid
dst cache overflows during DoS testing [as
explained in my OLS presentation ]
It will be easier to stick the two patches from Paul on top of these,
so I will merge these with my patchset and send the entire set
of 5 patches for -mm testing.
Thanks
Dipankar
next prev parent reply other threads:[~2004-08-04 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 14:28 [RFC][PATCH] Improve readability by hiding read_barrier_depends() calls Paul E. McKenney
2004-08-05 19:27 ` Dipankar Sarma [this message]
2004-08-04 20:43 ` Paul E. McKenney
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=20040805192756.GE3935@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=paulmck@us.ibm.com \
--cc=shemminger@osdl.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