From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: linux-nfs@vger.kernel.org,
Anna Schumaker <anna.schumaker@netapp.com>,
Jeff Layton <jlayton@poochiereds.net>,
Trond Myklebust <trond.myklebust@primarydata.com>
Subject: Re: [PATCH] SUNRPC: drop stale comment in svc_setup_socket()
Date: Tue, 27 Oct 2015 17:16:48 -0400 [thread overview]
Message-ID: <20151027211648.GE14022@fieldses.org> (raw)
In-Reply-To: <1445941410-28270-1-git-send-email-stefanha@redhat.com>
On Tue, Oct 27, 2015 at 10:23:30AM +0000, Stefan Hajnoczi wrote:
> Since 9660439861aa8dbd5e2b8087f33e20760c2c9afc ("svcrpc: take advantage
> of tcp autotuning") the svc_setup_socket() function does set the send
> and receive buffer sizes so the comment is out-of-date:
Hm, looks like it did it before too, just in svc_tcp_init instead.
Anyway, agreed that the comment doesn't look like much help, applying
your patch with a shorter changelog--thanks.
--b.
>
> /* initialise setting must have enough space to
> * receive and respond to one request.
> */
> svc_sock_setbufsize(svsk->sk_sock, 4 * serv->sv_max_mesg,
> 4 * serv->sv_max_mesg);
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> net/sunrpc/svcsock.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/net/sunrpc/svcsock.c b/net/sunrpc/svcsock.c
> index 0c81202..c7157eb 100644
> --- a/net/sunrpc/svcsock.c
> +++ b/net/sunrpc/svcsock.c
> @@ -1367,7 +1367,6 @@ EXPORT_SYMBOL_GPL(svc_sock_update_bufs);
>
> /*
> * Initialize socket for RPC use and create svc_sock struct
> - * XXX: May want to setsockopt SO_SNDBUF and SO_RCVBUF.
> */
> static struct svc_sock *svc_setup_socket(struct svc_serv *serv,
> struct socket *sock,
> --
> 2.4.3
prev parent reply other threads:[~2015-10-27 21:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 10:23 [PATCH] SUNRPC: drop stale comment in svc_setup_socket() Stefan Hajnoczi
2015-10-27 21:16 ` J. Bruce Fields [this message]
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=20151027211648.GE14022@fieldses.org \
--to=bfields@fieldses.org \
--cc=anna.schumaker@netapp.com \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@vger.kernel.org \
--cc=stefanha@redhat.com \
--cc=trond.myklebust@primarydata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.