From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Alex Shi <alex.shi@intel.com>
Cc: rusty@rustcorp.com.au, akpm@linux-foundation.org,
paul.gortmaker@windriver.com, kosaki.motohiro@jp.fujitsu.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpumask: add a few comments of cpumask functions
Date: Mon, 28 May 2012 18:17:21 +0530 [thread overview]
Message-ID: <4FC373D9.7040109@linux.vnet.ibm.com> (raw)
In-Reply-To: <1338195748-18934-1-git-send-email-alex.shi@intel.com>
On 05/28/2012 02:32 PM, Alex Shi wrote:
> Current few cpumask function purpose are not quite clear. Stupid
> user like myself need to dig into details for clear function
> purpose and return value.
You can just see how it is used elsewhere and figure it out ;-)
Anyway, in principle, I don't have any objections to adding comments
that are actually helpful. But I don't think all the comments this
patch adds fall into that category..
> Add few explanation for them is helpful.
>
> Signed-off-by: Alex Shi <alex.shi@intel.com>
> ---
> include/linux/cpumask.h | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/cpumask.h b/include/linux/cpumask.h
> index a2c819d..8436e61 100644
> --- a/include/linux/cpumask.h
> +++ b/include/linux/cpumask.h
> @@ -271,6 +271,7 @@ static inline void cpumask_clear_cpu(int cpu, struct cpumask *dstp)
> * cpumask_test_cpu - test for a cpu in a cpumask
> * @cpu: cpu number (< nr_cpu_ids)
> * @cpumask: the cpumask pointer
> + * return 1 if the 'cpu' is in the old 'cpumask', otherwise return 0
> *
s/return/Returns
What do you mean by "old" cpumask?
> * No static inline type checking - see Subtlety (1) above.
> */
> @@ -281,6 +282,7 @@ static inline void cpumask_clear_cpu(int cpu, struct cpumask *dstp)
> * cpumask_test_and_set_cpu - atomically test and set a cpu in a cpumask
> * @cpu: cpu number (< nr_cpu_ids)
> * @cpumask: the cpumask pointer
> + * return 1 if the 'cpu' is in the old 'cpumask', otherwise return 0
> *
"Test and Set" already has a very well-defined and well-known meaning.. Not sure if the
comment adds any extra value..
> * test_and_set_bit wrapper for cpumasks.
> */
> @@ -293,6 +295,7 @@ static inline int cpumask_test_and_set_cpu(int cpu, struct cpumask *cpumask)
> * cpumask_test_and_clear_cpu - atomically test and clear a cpu in a cpumask
> * @cpu: cpu number (< nr_cpu_ids)
> * @cpumask: the cpumask pointer
> + * return 1 if the 'cpu' is in the old 'cpumask', otherwise return 0
> *
Same here. Pretty well known meaning.
> * test_and_clear_bit wrapper for cpumasks.
> */
> @@ -324,6 +327,7 @@ static inline void cpumask_clear(struct cpumask *dstp)
> * @dstp: the cpumask result
> * @src1p: the first input
> * @src2p: the second input
> + * if *dstp is empty, return 0, otherwise return 1
I don't think anybody would be interested in the return value of this function!
The functionality (rather than the return value) is what is more interesting
and useful, and is already well-documented.
> */
> static inline int cpumask_and(struct cpumask *dstp,
> const struct cpumask *src1p,
> @@ -365,6 +369,7 @@ static inline void cpumask_xor(struct cpumask *dstp,
> * @dstp: the cpumask result
> * @src1p: the first input
> * @src2p: the second input
> + * if *dstp is empty, return 0, otherwise return 1
Same here. Functionality is more interesting.
> */
> static inline int cpumask_andnot(struct cpumask *dstp,
> const struct cpumask *src1p,
> @@ -414,6 +419,7 @@ static inline bool cpumask_intersects(const struct cpumask *src1p,
> * cpumask_subset - (*src1p & ~*src2p) == 0
> * @src1p: the first input
> * @src2p: the second input
> + * return 1 if the *src1p is the subset of *src2p, otherwise return 0
s/return/Returns
(I think the function name itself is pretty descriptive, but anyway...)
> */
> static inline int cpumask_subset(const struct cpumask *src1p,
> const struct cpumask *src2p)
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2012-05-28 12:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 9:02 Alex Shi
2012-05-28 12:47 ` Srivatsa S. Bhat [this message]
2012-05-28 13:49 ` Alex Shi
2012-05-28 14:23 ` Alex Shi
2012-07-13 22:37 ` Andrew Morton
2012-07-16 2:34 ` Alex Shi
2012-07-16 7:35 ` Rusty Russell
2012-07-16 8:01 ` Alex Shi
2012-05-28 15:25 ` Srivatsa S. Bhat
2012-05-29 1:16 ` Alex Shi
2012-05-30 10:40 ` Alex Shi
2012-05-30 10:49 ` KOSAKI Motohiro
2012-05-31 8:15 ` Alex Shi
2012-06-04 1:37 ` Rusty Russell
2012-06-04 1:36 ` Rusty Russell
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=4FC373D9.7040109@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rusty@rustcorp.com.au \
/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