From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [PATCH 1/3] kernel/srcu: merge common code into a macro
Date: Fri, 05 Apr 2013 15:21:27 +0800 [thread overview]
Message-ID: <515E7B77.7010807@cn.fujitsu.com> (raw)
In-Reply-To: <1363702606-31586-1-git-send-email-bigeasy@linutronix.de>
On 03/19/2013 10:16 PM, Sebastian Andrzej Siewior wrote:
> DEFINE_SRCU() and DEFINE_STATIC_SRCU() does the same thing except for
> the "static" attribute. This patch moves the common pieces into
> _DEFINE_SRCU() which is used by the the former macros either adding the
> static attribute or not.
>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
> include/linux/srcu.h | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
Hi, Sebastian
The patch hurts readability.
The original code are simple enough, merging them as one macro
gives us no benefit.
Thanks
Lai.
>
> diff --git a/include/linux/srcu.h b/include/linux/srcu.h
> index 6eb691b..d04acb8 100644
> --- a/include/linux/srcu.h
> +++ b/include/linux/srcu.h
> @@ -102,13 +102,13 @@ void process_srcu(struct work_struct *work);
> * define and init a srcu struct at build time.
> * dont't call init_srcu_struct() nor cleanup_srcu_struct() on it.
> */
> -#define DEFINE_SRCU(name) \
> +#define _DEFINE_SRCU(name, mod) \
> static DEFINE_PER_CPU(struct srcu_struct_array, name##_srcu_array);\
> - struct srcu_struct name = __SRCU_STRUCT_INIT(name);
> + mod struct srcu_struct name = \
> + __SRCU_STRUCT_INIT(name);
>
> -#define DEFINE_STATIC_SRCU(name) \
> - static DEFINE_PER_CPU(struct srcu_struct_array, name##_srcu_array);\
> - static struct srcu_struct name = __SRCU_STRUCT_INIT(name);
> +#define DEFINE_SRCU(name) _DEFINE_SRCU(name, )
> +#define DEFINE_STATIC_SRCU(name) _DEFINE_SRCU(name, static)
>
> /**
> * call_srcu() - Queue a callback for invocation after an SRCU grace period
next prev parent reply other threads:[~2013-04-05 7:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 14:16 Sebastian Andrzej Siewior
2013-03-19 14:16 ` [PATCH 2/3] kernel/SRCU: provide a static initializer Sebastian Andrzej Siewior
2013-04-05 7:21 ` Lai Jiangshan
2013-04-08 10:03 ` Sebastian Andrzej Siewior
2013-04-09 1:09 ` Lai Jiangshan
2013-04-11 17:04 ` Sebastian Andrzej Siewior
2013-04-12 2:56 ` Lai Jiangshan
2013-04-16 18:20 ` Paul E. McKenney
2013-03-19 14:16 ` [PATCH 3/3] cpufreq: use static initializer for the SRCU notifier Sebastian Andrzej Siewior
2013-03-19 16:22 ` [PATCH 1/3] kernel/srcu: merge common code into a macro Joe Perches
2013-03-19 18:15 ` Sebastian Andrzej Siewior
2013-04-05 7:21 ` Lai Jiangshan [this message]
2013-04-08 10:05 ` Sebastian Andrzej Siewior
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=515E7B77.7010807@cn.fujitsu.com \
--to=laijs@cn.fujitsu.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
/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
Powered by JetHome