Date: Tue, 29 Jul 2008 12:02:35 -0400 From: John Baldwin <jhb@freebsd.org> To: Julian Elischer <julian@elischer.org> Cc: cvs-src@freebsd.org, src-committers@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/kern sched_4bsd.c Message-ID: <200807291202.36185.jhb@freebsd.org> In-Reply-To: <488E5249.5010608@elischer.org> References: <200807282039.m6SKdU1T073711@repoman.freebsd.org> <200807281647.37400.jhb@freebsd.org> <488E5249.5010608@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 28 July 2008 07:12:09 pm Julian Elischer wrote: > John Baldwin wrote: > > On Monday 28 July 2008 04:39:21 pm John Baldwin wrote: > >> jhb 2008-07-28 20:39:21 UTC > >> > >> FreeBSD src repository > >> > >> Modified files: > >> sys/kern sched_4bsd.c > >> Log: > >> SVN rev 180937 on 2008-07-28 20:39:21Z by jhb > >> > >> When choosing a CPU for a thread in a cpuset, prefer the last CPU that the > >> thread ran on if there are no other CPUs in the set with a shorter per-CPU > >> runqueue. > > would this help teh case where we set up a cpu set with all CPUs? > > in other words shouldn't we just drop the single cpu runqueue > and have this always turned on? I'm not sure. I think that fundamentally changes 4BSD a lot (much more like ULE) and it's useful to keep around for comparison. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200807291202.36185.jhb>