From: Dipankar Sarma <dipankar@in.ibm.com>
To: "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, shemminger@osdl.org,
manfred@colorfullife.com, bunk@stusta.de
Subject: Re: [RFC,PATCH 2/4] Deprecate synchronize_kernel, GPL replacement
Date: Sun, 3 Apr 2005 14:26:50 +0530 [thread overview]
Message-ID: <20050403085650.GA4563@in.ibm.com> (raw)
In-Reply-To: <20050403062149.GA1656@us.ibm.com>
On Sat, Apr 02, 2005 at 10:21:50PM -0800, Paul E. McKenney wrote:
> The synchronize_kernel() primitive is used for quite a few different
> purposes: waiting for RCU readers, waiting for NMIs, waiting for interrupts,
> and so on. This makes RCU code harder to read, since synchronize_kernel()
> might or might not have matching rcu_read_lock()s. This patch creates
> a new synchronize_rcu() that is to be used for RCU readers and a new
> synchronize_sched() that is used for the rest. These two new primitives
> currently have the same implementation, but this is might well change
> with additional real-time support. Both new primitives are GPL-only,
> the old primitive is deprecated.
>
> Signed-off-by: <paulmck@us.ibm.com>
> ---
> Depends on earlier "Add deprecated_for_modules" patch.
>
> +/*
> + * Deprecated, use synchronize_rcu() or synchronize_sched() instead.
> + */
> +void synchronize_kernel(void)
> +{
> + synchronize_rcu();
> +}
> +
We should probably mark it deprecated -
void __deprecated synchronize_kernel(void)
{
synchronize_rcu();
}
Thanks
Dipankar
next prev parent reply other threads:[~2005-04-03 8:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-03 6:21 [RFC,PATCH 2/4] Deprecate synchronize_kernel, GPL replacement Paul E. McKenney
2005-04-03 8:56 ` Dipankar Sarma [this message]
2005-04-03 18:50 ` Paul E. McKenney
2005-04-03 22:26 ` Arnd Bergmann
2005-04-04 21:13 ` Paul E. McKenney
2005-04-03 14:11 ` Michael Ellerman
2005-04-03 18:54 ` 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=20050403085650.GA4563@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.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