Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759973AbYJINke (ORCPT ); Thu, 9 Oct 2008 09:40:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758851AbYJINkX (ORCPT ); Thu, 9 Oct 2008 09:40:23 -0400 Received: from hs-out-0708.google.com ([64.233.178.242]:10072 "EHLO hs-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758815AbYJINkW (ORCPT ); Thu, 9 Oct 2008 09:40:22 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references:x-google-sender-auth; b=Fy9DFqtxbmUTltvgIRLX4pkUh5r6XjrXPFjH7Etj0s3IDmQgNXVE0MTy5RRUTvqEYh 4SzG2//KF7/ENg66mMOh+CZH9B9u3qYCAeg9vTePFYPGM/GL08tndzt5HpV72/UCPBJs cM9+m1fAu3JQ5WczrarXINwNReiiOkwdxS2h0= Message-ID: Date: Thu, 9 Oct 2008 07:40:18 -0600 From: "Latchesar Ionkov" To: "Eric Van Hensbergen" Subject: Re: [V9fs-developer] [PATCH 04/10] 9p: move dirread to fs layer Cc: linux-kernel@vger.kernel.org, v9fs-developer@lists.sourceforge.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1223500147-19654-5-git-send-email-ericvh@gmail.com> X-Google-Sender-Auth: 84001a8bc56abd0a Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2032 Lines: 42 I don't think that there is anything at the moment that uses dirread, but the remote framebuffer that Abishek is working on uses some other of the client operations. Thanks, Lucho On Wed, Oct 8, 2008 at 5:12 PM, Eric Van Hensbergen wrote: > On Wed, Oct 8, 2008 at 5:10 PM, Latchesar Ionkov wrote: >> The idea of the client implementation is to be able to use it not only >> from the vfs layer, but also without it. For example, creating a >> device that connect to a remote 9P file server. >> > > That does make sense in principal -- although I'm not sure filldir > structures are the easiest things to work with either. The main idea > was to restrict the client.c code to wire operations, primarily > torwards the idea of treating the "client" as a proxy server once the > in-kernel-server code goes in (hopefully in 2.6.29). > Of course the other factor is that this patch-set is gearing up > towards an alternate extended-POSIX-support approach (what I've been > referring to as .L) -- that extension will include a wire operation > which more closely matches linux's concept of dirread (just grab the > files, not the associated stat) -- but whether or not that is useful > will largely depend on what sort of remote server you are accessing. > > The Plan 9 dirread is one of those special cases where even though its > not a wire operation, it needs some intimate understanding of the > underlying protocol (at least how stats get marshalled) -- in some > ways if it were a client operation, it might make more sense to pass > it an array of p9_stat structs to populate with the results. > > Do you have some code which used the old client interface I could look > at or were you just thinking towards the future? > > -eric > -- 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/