mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Eric Van Hensbergen" <ericvh@gmail.com>
To: "Latchesar Ionkov" <lucho@ionkov.net>
Cc: linux-kernel@vger.kernel.org, v9fs-developer@lists.sourceforge.net
Subject: Re: [V9fs-developer] [PATCH 04/10] 9p: move dirread to fs layer
Date: Wed, 8 Oct 2008 18:12:17 -0500	[thread overview]
Message-ID: <a4e6962a0810081612i7f30ec16gf727da56816530ab@mail.gmail.com> (raw)
In-Reply-To: <f158dc670810081510t3b5be588v8298aa20a26039c5@mail.gmail.com>

On Wed, Oct 8, 2008 at 5:10 PM, Latchesar Ionkov <lucho@ionkov.net> 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

  reply	other threads:[~2008-10-08 23:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1223500147-19654-5-git-send-email-ericvh@gmail.com>
2008-10-08 22:10 ` Latchesar Ionkov
2008-10-08 23:12   ` Eric Van Hensbergen [this message]
2008-10-09 13:40     ` Latchesar Ionkov
2008-10-09 14:10       ` Eric Van Hensbergen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a4e6962a0810081612i7f30ec16gf727da56816530ab@mail.gmail.com \
    --to=ericvh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lucho@ionkov.net \
    --cc=v9fs-developer@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®