Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756893AbYKESVS (ORCPT ); Wed, 5 Nov 2008 13:21:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752019AbYKESVF (ORCPT ); Wed, 5 Nov 2008 13:21:05 -0500 Received: from terminus.zytor.com ([198.137.202.10]:47446 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752621AbYKESVE (ORCPT ); Wed, 5 Nov 2008 13:21:04 -0500 Message-ID: <4911E3E7.6090109@zytor.com> Date: Wed, 05 Nov 2008 10:20:23 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 2.0.0.14 (X11/20080501) MIME-Version: 1.0 To: Cyrill Gorcunov CC: Ingo Molnar , Alexander van Heukelum , Andi Kleen , Alexander van Heukelum , LKML , Thomas Gleixner , lguest@ozlabs.org, jeremy@xensource.com, Steven Rostedt , Mike Travis Subject: Re: [PATCH RFC/RFB] x86_64, i386: interrupt dispatch changes References: <20081104122839.GA22864@mailshack.com> <20081104150729.GC21470@localhost> <20081104170501.GE29626@one.firstfloor.org> <1225822006.21441.1282961299@webmail.messagingengine.com> <20081104204400.GC10825@elte.hu> <20081104212933.GA11050@elte.hu> <4910C014.9070805@zytor.com> <20081104215245.GC17775@elte.hu> <20081105175318.GD7286@localhost> <4911E042.8040404@zytor.com> <20081105181405.GE7286@localhost> In-Reply-To: <20081105181405.GE7286@localhost> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1104 Lines: 26 Cyrill Gorcunov wrote: > > I see. Thanks! Btw Peter, I remember I read long time ago about > segment caches (well... in time of DOS programming actually). But > there was only 'common' words like this cache exist. But maybe > it's possible to know what exactly size of such a cache is? > You mentoined number 32. (heh... I hadn't remember it until > you mentoined about such a cache :-) > As with any other caching structure, you can discover its size, associativity, and replacement policy by artificially trying to provoke patterns that produce pathological timings. At Transmeta, at one time we used a 32-entry direct-mapped cache, which ended up with a ~96% hit rate on common Win95 benchmarks. I should, however, make it clear that there are other alternatives for speeding up segment descriptor loading, and not all of them rely on a cache. -hpa -- 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/