Re: [PATCH] Force rcutorture tasks to spread over CPUs

On Tue, 12 Jun 2007 21:28:04 -0700
"Paul E. McKenney" <[email protected]> wrote:

> +	while (!startwriters)
> +		barrier();	/* Force scheduler to spread over CPUs. */

one wonders whether a cpu_relax() would be a bit nicer here.  That implicitly
does a barrier().

This patch doesn't make much sense for non-SMP builds?
-
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] Force rcutorture tasks to spread over CPUs
  - From: Ingo Molnar <[email protected]>

References:
- [PATCH] Force rcutorture tasks to spread over CPUs
  - From: "Paul E. McKenney" <[email protected]>

Prev by Date: [AppArmor 43/44] Switch to vfs_permission() in sys_fchdir()
Next by Date: [AppArmor 04/44] Pass struct vfsmount to the inode_setattr LSM hook
Previous by thread: Re: [PATCH] Force rcutorture tasks to spread over CPUs
Next by thread: Re: [PATCH] Force rcutorture tasks to spread over CPUs
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]