On 7/28/05, Ronald G. Minnich wrote:
>
>
> On Thu, 28 Jul 2005, Christoph Hellwig wrote:
>
> > Couldn't the two other transports be implemented ontop of this one using
> > a mount helper doing the pipe or tcp setup?
>
> that's how we did it in the version we did for 2.4. I don't see why not.
>
> +static int v9fs_fd_recv(struct v9fs_transport *trans, void *v, int len)
> +{
> + struct v9fs_trans_fd *ts = trans ? trans->priv : NULL;
> +
> + return kernel_read(ts->in_file, ts->in_file->f_pos, v, len);
> +}
> +static int v9fs_fd_send(struct v9fs_transport *trans, void *v, int le
On Thu, 28 Jul 2005, Christoph Hellwig wrote:
> Couldn't the two other transports be implemented ontop of this one using
> a mount helper doing the pipe or tcp setup?
that's how we did it in the version we did for 2.4. I don't see why not.
ron
-
To unsubscribe from this list: send the line "un
On Thu, Jul 28, 2005 at 08:57:23AM -0500, [EMAIL PROTECTED] wrote:
> v9fs: add file-descriptor based transport as was requested by LANL and
> Plan 9 from User Space folks.
Couldn't the two other transports be implemented ontop of this one using
a mount helper doing the pipe or tcp setup?
-
To uns
v9fs: add file-descriptor based transport as was requested by LANL and
Plan 9 from User Space folks.
Signed-off-by: Eric Van Hensbergen <[EMAIL PROTECTED]>
---
commit e65b41c8081e0f7227a16d39a4bc65e2924d7680
tree 4cfd78c690d2e9852736499fe9d0a311c78beee8
parent eefccf73f82b2bdf353cd05b8e5d6142210b
5 matches
Mail list logo
