From: Andi Kleen <andi@firstfloor.org>
To: "Julio M. Merino Vidal" <jmerino@ac.upc.edu>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: Per-CPU data as a structure
Date: Fri, 4 May 2007 16:07:53 +0200 [thread overview]
Message-ID: <20070504140753.GA4344@one.firstfloor.org> (raw)
In-Reply-To: <463AF095.30406@ac.upc.edu>
> +/*
> + * percpu provides a mechanism to define variables that are specific to
> each
> + * CPU in the system.
> + *
> + * Each variable is defined as an independent array of NR_CPUS elements.
The independent array term seems misleading to me. There isn't really
an array anywhere. Perhaps explain it in more details.
If you write documentation please write it in Kerneldoc format so
that it can be automatically extracted. See
Documentation/kernel-doc-nano-HOWTO.txt
-Andi
prev parent reply other threads:[~2007-05-04 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 15:16 Per-CPU data as a structure Julio M. Merino Vidal
2007-05-03 17:19 ` Andi Kleen
2007-05-04 8:36 ` Julio M. Merino Vidal
2007-05-04 8:55 ` Eric Dumazet
2007-05-04 14:07 ` Andi Kleen [this message]
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=20070504140753.GA4344@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=jmerino@ac.upc.edu \
--cc=linux-kernel@vger.kernel.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