From: Benny Halevy <bhalevy@panasas.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: pnfs@linux-nfs.org, linux-nfs@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [pnfs] [RFC 01/85] sunrpc: get rid of rpc_rqst.rq_bufsize
Date: Tue, 18 Nov 2008 10:42:13 +0200 [thread overview]
Message-ID: <49227FE5.3070304@panasas.com> (raw)
In-Reply-To: <49216F05.4090706@panasas.com>
On Nov. 17, 2008, 15:17 +0200, Benny Halevy <bhalevy@panasas.com> wrote:
> On Nov. 10, 2008, 21:59 +0200, Benny Halevy <bhalevy@panasas.com> wrote:
>> rq_bufsize is not used.
>>
>> Signed-off-by: Mike Sager <Mike.Sager@netapp.com>
>> Signed-off-by: Benny Halevy <bhalevy@panasas.com>
>> ---
>> include/linux/sunrpc/xprt.h | 3 +--
>> 1 files changed, 1 insertions(+), 2 deletions(-)
>>
>> diff --git a/include/linux/sunrpc/xprt.h b/include/linux/sunrpc/xprt.h
>> index 4d80a11..11fc71d 100644
>> --- a/include/linux/sunrpc/xprt.h
>> +++ b/include/linux/sunrpc/xprt.h
>> @@ -76,8 +76,7 @@ struct rpc_rqst {
>> struct list_head rq_list;
>>
>> __u32 * rq_buffer; /* XDR encode buffer */
>> - size_t rq_bufsize,
>
> review 11-14: this was used in the past as a sanity check.
> find out when/why this functionality was ripped out.
Since commit c5a4dd8b7c15927a8fbff83171b57cad675a79b9
we encode the buffer size "inline", prepending the buffer contents.
Therefore there is indeed no use of rq_bufsize anymore.
Benny
>
>> - rq_callsize,
>> + size_t rq_callsize,
>> rq_rcvsize;
>>
>> struct xdr_buf rq_private_buf; /* The receive buffer
>> --
>> 1.6.0.1
>>
> --
> 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
prev parent reply other threads:[~2008-11-18 8:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 19:59 [RFC 01/85] sunrpc: get rid of rpc_rqst.rq_bufsize Benny Halevy
2008-11-17 13:17 ` [pnfs] " Benny Halevy
2008-11-18 8:42 ` Benny Halevy [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=49227FE5.3070304@panasas.com \
--to=bhalevy@panasas.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=pnfs@linux-nfs.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