From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 24 Jan 2003 03:41:46 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 24 Jan 2003 03:41:46 -0500 Received: from [210.212.228.4] ([210.212.228.4]:37304 "EHLO cnet.nitc.ac.in") by vger.kernel.org with ESMTP id ; Fri, 24 Jan 2003 03:41:45 -0500 Message-ID: <54208.210.212.228.78.1043398260.webmail@mail.nitc.ac.in> Date: Fri, 24 Jan 2003 14:21:00 +0530 (IST) Subject: Re: your mail From: "Anoop J." To: In-Reply-To: References: <42636.210.212.228.78.1043387664.webmail@mail.nitc.ac.in> Cc: , X-Mailer: nitc webmail (version 1.2.7) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org I read that the data coherency problem due to virtual indexing is avoided through page coloring and it has also got the speed of physical indexing can u just elaborate on how this is possible? Thanks > implementing a fully associative cache eliminates the need for page > coloring, but it has to be implemented in hardware. if you don't have > fully associative caches in your hardware page coloring helps avoid the > worst case memory allocations. > > from what I have seen on the attempts to implement it the problem is > that the calculations needed to do page colored allocations end up > costing enough that they end up with a net loss compared to the old > method. > > David Lang > > > On Fri, 24 Jan 2003, Anoop J. > wrote: > >> Date: Fri, 24 Jan 2003 11:24:24 +0530 (IST) >> From: Anoop J. >> To: linux-mm@kvack.org, linux-kernel@vger.kernel.org >> >> >> How is this different from a fully associative cache .Would be better >> if u could deal it based on the address bits used >> From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <54208.210.212.228.78.1043398260.webmail@mail.nitc.ac.in> Date: Fri, 24 Jan 2003 14:21:00 +0530 (IST) Subject: Re: your mail From: "Anoop J." In-Reply-To: References: <42636.210.212.228.78.1043387664.webmail@mail.nitc.ac.in> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org Return-Path: To: david.lang@digitalinsight.com Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org List-ID: I read that the data coherency problem due to virtual indexing is avoided through page coloring and it has also got the speed of physical indexing can u just elaborate on how this is possible? Thanks > implementing a fully associative cache eliminates the need for page > coloring, but it has to be implemented in hardware. if you don't have > fully associative caches in your hardware page coloring helps avoid the > worst case memory allocations. > > from what I have seen on the attempts to implement it the problem is > that the calculations needed to do page colored allocations end up > costing enough that they end up with a net loss compared to the old > method. > > David Lang > > > On Fri, 24 Jan 2003, Anoop J. > wrote: > >> Date: Fri, 24 Jan 2003 11:24:24 +0530 (IST) >> From: Anoop J. >> To: linux-mm@kvack.org, linux-kernel@vger.kernel.org >> >> >> How is this different from a fully associative cache .Would be better >> if u could deal it based on the address bits used >> -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/