Re: [PATCH] Optimize sys_times for a single thread process

On Wed, 18 May 2005, Oleg Nesterov wrote:

> Christoph Lameter wrote:
> >
> > +#ifdef CONFIG_SMP
> > +		if (current == next_thread(current)) {
> > +			/*
> > +			 * Single thread case without the use of any locks.
> 
> A nitpick, but wouldn't be it clearer to to use
> thread_group_empty(current)?

The thread ist needs to contain only one element which is current.
thread_group_empty checks for no threads.

Do we need a new macro?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] Optimize sys_times for a single thread process
    • From: Oleg Nesterov <[email protected]>

• References:
  • Re: [PATCH] Optimize sys_times for a single thread process
    • From: Oleg Nesterov <[email protected]>

• Prev by Date: Re: What is needed to boot 2.6 on opteron dual core
• Next by Date: Re: [RFC] Cachemap for 2.6.12rc4-mm1. Was Re: [PATCH] enhance x86 MTRR handling
• Previous by thread: Re: [PATCH] Optimize sys_times for a single thread process
• Next by thread: Re: [PATCH] Optimize sys_times for a single thread process
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]