Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750835AbWEDBfM (ORCPT ); Wed, 3 May 2006 21:35:12 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750837AbWEDBfM (ORCPT ); Wed, 3 May 2006 21:35:12 -0400 Received: from smtp.osdl.org ([65.172.181.4]:29610 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S1750835AbWEDBfK (ORCPT ); Wed, 3 May 2006 21:35:10 -0400 Date: Wed, 3 May 2006 18:31:37 -0700 (PDT) From: Linus Torvalds To: Linda Walsh cc: Wu Fengguang , linux-kernel@vger.kernel.org, Andrew Morton , Jens Axboe , Nick Piggin , Badari Pulavarty Subject: Re: [RFC] kernel facilities for cache prefetching In-Reply-To: <44594AA9.8020906@tlinx.org> Message-ID: References: <346556235.24875@ustc.edu.cn> <44594AA9.8020906@tlinx.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 913 Lines: 24 On Wed, 3 May 2006, Linda Walsh wrote: > > > - it gives you only a very limited view into what is actually going on. > > ??? In what way? I don't think we need a *complex* view of what > is going on. The block-based view is a very simple one, but it's _too_ simple. It doesn't actually tell the user what is happening. It doesn't tell you why the request happened in the first place, so it leaves you no way to really do anything sane about it. You can't prefetch (because the indexing is wrong), and you can't actually even analyze it (because you don't know any background to what you're seeing). In short, you can't _do_ anything with it. Linus - 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/