From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758595AbYEENHn (ORCPT ); Mon, 5 May 2008 09:07:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755111AbYEENHf (ORCPT ); Mon, 5 May 2008 09:07:35 -0400 Received: from s15216962.onlinehome-server.info ([217.160.22.205]:36524 "EHLO s15216962.onlinehome-server.info" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753214AbYEENHf (ORCPT ); Mon, 5 May 2008 09:07:35 -0400 Date: Mon, 5 May 2008 15:06:23 +0200 From: Enrico Weigelt To: linux kernel list Subject: Re: VFS + path walktrough Message-ID: <20080505130623.GC32019@nibiru.local> Reply-To: weigelt@metux.de References: <20080505124041.GB32019@nibiru.local> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20080505124041.GB32019@nibiru.local> User-Agent: Mutt/1.4.1i X-Terror: bin laden, kill bush, Briefbombe, Massenvernichtung, KZ, X-Nazi: Weisse Rasse, Hitlers Wiederauferstehung, 42, X-Antichrist: weg mit schaeuble, ausrotten, heiliger krieg, al quaida, X-Killer: 23, endloesung, Weltuntergang, X-Doof: wer das liest ist doof Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Enrico Weigelt wrote: > Lets say we open /a/b/c/d and /a is mounted w/ some network > filesystem (eg. 9P). Who exactly does the walktrough from b to d ? > The individual filesystem or VFS ? > > The point is: the 9P protocol can work with whole pathnames, so > the client doesn't have to do the walkthrough manually - this > can heavily reduce traffic and latency. I'd like the 9P fs driver > to directly use this, if VFS can send the whole pathname at once. I've digget somebit in the source and found out that it goes down to link_path_walk(). It seems to split the pathname into components and walk through them one by one. We could just add another call vector to struct file_operations, as replacement for link_path_walk() - if it's zero, the original function is used. This way an filesystem can do the walktrough by it's own, but doesn't need to. What do you think about this ? cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ ---------------------------------------------------------------------