From: Greg Banks <gnb@sgi.com>
To: Tom Tucker <tom@opengridcomputing.com>
Cc: Neil Brown <neilb@suse.de>,
Thomas Talpey <Thomas.Talpey@netapp.com>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Peter Leckie <pleckie@melbourne.sgi.com>,
Greg Banks <gnb@sgi.com>
Subject: Re: [RFC,PATCH 5/14] knfsd: max_payload per transport
Date: Tue, 22 May 2007 17:16:17 +1000 [thread overview]
Message-ID: <20070522071617.GE1202@sgi.com> (raw)
In-Reply-To: <1179415386.23385.5.camel@trinity.ogc.int>
On Thu, May 17, 2007 at 10:23:06AM -0500, Tom Tucker wrote:
> On Thu, 2007-05-17 at 20:34 +1000, Neil Brown wrote:
> > On Thursday May 17, gnb@sgi.com wrote:
> > >
> > > Make svc_max_payload() delegate to a new method in svc_sock_ops
> > > instead of reaching into the socket (beause later the NFS/RDMA
> > > transport will not even have a socket).
> > >
> > > Signed-off-by: Greg Banks <gnb@melbourne.sgi.com>
> > > Signed-off-by: Peter Leckie <pleckie@melbourne.sgi.com>
> > ..
> > >
> > > +static u32 svc_tcp_max_payload(struct svc_sock *svsk)
> > > +{
> > > + return RPCSVC_MAXPAYLOAD_TCP;
> > > +}
> > > +
> >
> > Seeing these are implementation (or protocol) defined constants, do we
> > really need a function call? How about a
> > int max_payload;
> > in struct svc_sock_ops?? Or is it tacky to put an integer in a *_ops
> > structure?
>
> I think if we called it a "svc_transport" structure instead of a
> "svc_sock_ops" structure, it removes the tackiness. It's also more
> accurate since "svc_sock_ops" implies these are socket ops which they
> are not.
I like this idea, so I renamed
svc_sock_ops -> svc_transport_type
sko_foo -> st_foo
sk_ops -> sk_type
Greg.
--
Greg Banks, R&D Software Engineer, SGI Australian Software Group.
Apparently, I'm Bedevere. Which MPHG character are you?
I don't speak for SGI.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-05-22 7:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 19:23 [RFC,PATCH 5/14] knfsd: max_payload per transport Greg Banks
2007-05-17 10:34 ` Neil Brown
2007-05-17 15:23 ` Tom Tucker
2007-05-22 7:16 ` Greg Banks [this message]
2007-05-18 4:56 ` Greg Banks
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=20070522071617.GE1202@sgi.com \
--to=gnb@sgi.com \
--cc=Thomas.Talpey@netapp.com \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=pleckie@melbourne.sgi.com \
--cc=tom@opengridcomputing.com \
/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