From: Tom Tucker <tom@opengridcomputing.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Chuck Lever <chuck.lever@oracle.com>,
bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: [RFC,PATCH] svc: Modify svc_xprt_create to take a sockaddr
Date: Mon, 21 Jan 2008 12:22:53 -0600 [thread overview]
Message-ID: <1200939773.11003.53.camel@trinity.ogc.int> (raw)
In-Reply-To: <1200938366.25562.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
On Mon, 2008-01-21 at 12:59 -0500, Trond Myklebust wrote:
> On Mon, 2008-01-21 at 12:47 -0500, Chuck Lever wrote:
>
> > This is sort of a generic question.
> >
> > The server-side interface appears to be using strings to identify
> > transports ("tcp"), but the client-side is still using numbers
> > (XPRT_TRANSPORT_TCP). There are one or two sticky issues to fix
> > before the client-side can use strings, but...
>
> We already have to parse the mount string in the NFS code. Why on earth
> would we want to have a second parser for the same thing in the RPC
> code?
>
I don't. Oversight on my part....I'll recode with the existing
functions...
> Trond
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-01-21 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 17:11 [RFC,PATCH] svc: Modify svc_xprt_create to take a sockaddr Tom Tucker
[not found] ` <20080121171105.29028.61809.stgit-gUwIgmpLGaKNDNWfRnPdfg@public.gmane.org>
2008-01-21 17:47 ` Chuck Lever
2008-01-21 17:59 ` Trond Myklebust
[not found] ` <1200938366.25562.14.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-21 18:22 ` Tom Tucker [this message]
2008-01-21 18:30 ` Chuck Lever
2008-01-21 19:24 ` Trond Myklebust
[not found] ` <1200943495.25562.52.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-21 20:48 ` Tom Tucker
[not found] ` <1200948494.11003.71.camel-SMNkleLxa3ZimH42XvhXlA@public.gmane.org>
2008-01-21 22:42 ` Trond Myklebust
[not found] ` <1200955371.27963.28.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org>
2008-01-22 17:52 ` Chuck Lever
2008-01-21 18:21 ` Tom Tucker
2008-01-21 18:35 ` J. Bruce Fields
2008-01-21 19:15 ` Tom Tucker
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=1200939773.11003.53.camel@trinity.ogc.int \
--to=tom@opengridcomputing.com \
--cc=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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