Messages in this thread | | | Subject | RE: [PATCH] 2.6.0 batch scheduling, HT aware | Date | Mon, 22 Dec 2003 21:33:37 -0800 | From | "Nakajima, Jun" <> |
| |
BTW, Nick, does your SMT scheduler have "idle package prioritization" which chooses an idle logical processor with the other local processor idle if any (rather than just an idle processor with other local processor running at full speed), when the scheduler requires an idle local processor? That would prevent situations like two logical processors run at full speed in the same processor package, with the other processor package(s) idle in a same processor package(s). I haven't reviewed your latest patch closely, and that is the one of the things I want to do during the holidays.
One question. Why did you remove SD_FLAG_IDLE flag from cpu_domain initialization in the w27 patch? We've been seeing some performance degradation with w27, compared to w26.
Jun
> -----Original Message----- > From: Nick Piggin [mailto:piggin@cyberone.com.au] > Sent: Monday, December 22, 2003 6:41 PM > To: Nakajima, Jun > Cc: Con Kolivas; linux kernel mailing list > Subject: Re: [PATCH] 2.6.0 batch scheduling, HT aware > > > > Nakajima, Jun wrote: > > >Today utilization of execution resources of a logical processor is > >around 60% as you can find in public papers, and it's dependent on the > >processor implementation and the workload. It could be higher in the > >future, and their relative priority could be much higher then. So I > >don't think it's a good idea to hard code such a implementation-specific > >factor into the generic scheduler code. > > > > No. The mechanism would be generic, but the parameters would be > arch specific as part of my sched domains patch (if I have anything > to do with it!) >
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |