Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261230AbUCALzQ (ORCPT ); Mon, 1 Mar 2004 06:55:16 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261238AbUCALzQ (ORCPT ); Mon, 1 Mar 2004 06:55:16 -0500 Received: from mail-04.iinet.net.au ([203.59.3.36]:56032 "HELO mail.iinet.net.au") by vger.kernel.org with SMTP id S261230AbUCALzG (ORCPT ); Mon, 1 Mar 2004 06:55:06 -0500 Message-ID: <4043227A.6050806@cyberone.com.au> Date: Mon, 01 Mar 2004 22:46:02 +1100 From: Nick Piggin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1 X-Accept-Language: en MIME-Version: 1.0 To: Con Kolivas CC: linux kernel mailing list , Andrew Morton Subject: Re: [PATCH] SMT Nice 2.6.4-rc1-mm1 References: <200403011752.56600.kernel@kolivas.org> <200403012225.59538.kernel@kolivas.org> <4043205C.7050109@cyberone.com.au> <200403012240.34535.kernel@kolivas.org> In-Reply-To: <200403012240.34535.kernel@kolivas.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1687 Lines: 48 Con Kolivas wrote: >On Mon, 1 Mar 2004 10:37 pm, Nick Piggin wrote: > >>Con Kolivas wrote: >> >>>On Mon, 1 Mar 2004 05:52 pm, Con Kolivas wrote: >>> >>>>This patch provides full per-package priority support for SMT processors >>>>(aka pentium4 hyperthreading) when combined with CONFIG_SCHED_SMT. >>>> >>>And here are some benchmarks to demonstrate what happens. >>>P4 3.06Ghz booted with bios HT off as UP (up), SMP with mm1(mm1), SMP with >>>mm1-smtnice(sn) >>> >>Pretty impressive numbers. >> >>How does it go on the desktop when running mprime at nice +19? >>How much worse can latencies of the niced tasks become? Any idea? >> > >Worst case scenario is easy to model; if a nice -19 task starts at exactly the >same time as a nice +19 task, the timeslices are 200 and 10ms. On >uniprocessor the nice+19 task will wait _at least_ 200 ms. On SMT nice SMP it >will be 200 - (200 * 15 / 100) so 170ms. That is of course worst case >scenario and still better than UP since the latency will be less, the task >will definitely start (interactive reinsertion wont affect it) and it will be >on a second runqueue. > > OK thats good. I'm still not exactly how to generalise the cpu power / impact stuff, but that isn't critical. It should be done some time though. I'd be happy to see this patch in -mm. As Con mentioned, it would be probably good to merge it one major release after base sched domains is merged (if ever). Thanks Con. - 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/