Re: [PATCH 19/25] Docs: kernel-hacking: CPU id on [0,NR_CPUS)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 4 Mar 2010 02:19:37 -0600 Michael Witten wrote:

> On Thu, Mar 4, 2010 at 01:33, Michael Witten <mfwitten@xxxxxxxxx> wrote:
> > +    <function>get_cpu()</function> disables preemption on the local CPU
> > +    (so you won't suddenly get moved to another CPU) and then returns
> > +    the local CPU id as a number ranging from 0 up to (but not including)
> > +    <symbol>NR_CPUS</symbol>; subsequently returned CPU ids are not
> > +    necessarily contiguous.
> 
> It occurred to me that the original 'continuous' means 'constant'
> rather than 'contiguous'. However, given the introduction of the term
> 'local CPU', I don't think that this sentence is even necessary
> anymore. How about just removing it?
> --

Remove that entire paragraph (above) or just the "subsequently returned
CPU ids are not necessarily contiguous." part of it?  Removing the latter
makes sense to me.

---
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux