From: "J. Bruce Fields" <bfields@fieldses.org>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: neilb@suse.de, nfs@lists.sourceforge.net
Subject: Re: [PATCH 15/23] mount.nfs: clean up getport() function
Date: Sun, 29 Jul 2007 19:43:33 -0400 [thread overview]
Message-ID: <20070729234333.GA18686@fieldses.org> (raw)
In-Reply-To: <20070728215024.21871.54208.stgit@localhost.localdomain>
On Sat, Jul 28, 2007 at 05:50:24PM -0400, Chuck Lever wrote:
> Mostly comment clarification. Also replace some naked undocumented
> integers with macros, and make getport() static.
> @@ -153,25 +157,30 @@ unsigned short getport(struct sockaddr_in *saddr, unsigned long prog,
> return 0;
> }
>
> - switch (prot) {
> + switch (proto) {
> case IPPROTO_UDP:
> clnt = clntudp_bufcreate(saddr,
> - PMAPPROG, PMAPVERS, TIMEOUT, &socket,
> - UDPMSGSIZE, UDPMSGSIZE);
> + PMAPPROG, PMAPVERS,
> + RETRY_TIMEOUT, &socket,
> + RPCSMALLMSGSIZE,
> + RPCSMALLMSGSIZE);
> break;
> case IPPROTO_TCP:
> - clnt = clnttcp_create(saddr,
> - PMAPPROG, PMAPVERS, &socket, 50, 500);
> + clnt = clnttcp_create(saddr, PMAPPROG, PMAPVERS, &socket,
> + RPCSMALLMSGSIZE, RPCSMALLMSGSIZE);
Did you mean to change those final two arguments? (They were different
before, then they're the same after.)
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-07-29 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 21:50 [PATCH 15/23] mount.nfs: clean up getport() function Chuck Lever
2007-07-29 23:43 ` J. Bruce Fields [this message]
2007-07-30 2:33 ` Chuck Lever
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=20070729234333.GA18686@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=neilb@suse.de \
--cc=nfs@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