From: Trond Myklebust <trondmy@hammerspace.com>
To: "chuck.lever@oracle.com" <chuck.lever@oracle.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>
Subject: Re: [PATCH 2/4] SUNRPC: Widen rpc_task::tk_flags
Date: Sat, 23 Jul 2022 20:10:16 +0000 [thread overview]
Message-ID: <9bbefaf99fa4857a7718bea72127b5dd64e72898.camel@hammerspace.com> (raw)
In-Reply-To: <F3BA47F3-DE56-45DA-8E4A-4E8A65D5541A@oracle.com>
On Fri, 2022-07-22 at 17:55 +0000, Chuck Lever III wrote:
>
>
> > On Jul 22, 2022, at 1:53 PM, Trond Myklebust
> > <trondmy@hammerspace.com> wrote:
> >
> > On Fri, 2022-07-22 at 13:25 -0400, Chuck Lever wrote:
> > > There is just one unused bit left in rpc_task::tk_flags, and I
> > > will
> > > need two in subsequent patches. Double the width of the field to
> > > accommodate more flag bits.
> >
> > The values 0x8 and 0x40 are both free, so I'm not seeing why this
> > patch
> > is needed at this time.
>
> It's not needed now, but as recently as last year, there were no free
> bits (and I needed them for RPC-with-TLS support at that time). We
> will
> have to widen this field sooner or later.
>
> I don't have a problem dropping this one if you'd rather wait.
>
I dropped it after applying the other v2 patches. As I said, I don't
see a need for this expansion yet, and if we do at some point run out
of bits, I can see other flags we can drop (RPC_TASK_ROOTCREDS and
RPC_TASK_NULLCREDS being obvious targets) before we need to consider
actually expanding the size of this field.
In fact, by not expanding it, we can trivially shrink the size of
struct rpc_task by 8 bytes on x86_64 simply by moving the field
tk_rpc_status to eliminate the current 4 byte hole. I've added a patch
to do just that.
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next prev parent reply other threads:[~2022-07-23 20:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 17:25 [PATCH 0/4] Pre-requisites for client-side RPC-with-TLS support Chuck Lever
2022-07-22 17:25 ` [PATCH 1/4] SUNRPC: Fail faster on bad verifier Chuck Lever
2022-07-22 17:25 ` [PATCH 2/4] SUNRPC: Widen rpc_task::tk_flags Chuck Lever
2022-07-22 17:53 ` Trond Myklebust
2022-07-22 17:55 ` Chuck Lever III
2022-07-23 20:10 ` Trond Myklebust [this message]
2022-07-25 13:17 ` Chuck Lever III
2022-07-22 17:25 ` [PATCH 3/4] SUNRPC: Replace dprintk() call site in xs_data_ready Chuck Lever
2022-07-22 17:59 ` Trond Myklebust
2022-07-22 18:45 ` Chuck Lever III
2022-07-22 20:22 ` Steven Rostedt
2022-07-25 15:49 ` Arnaldo Carvalho de Melo
2022-07-25 16:06 ` Steven Rostedt
2022-07-22 17:25 ` [PATCH 4/4] NFS: Replace fs_context-related dprintk() call sites with tracepoints Chuck Lever
2022-07-22 18:00 ` Trond Myklebust
2022-07-22 19:05 ` Chuck Lever III
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=9bbefaf99fa4857a7718bea72127b5dd64e72898.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=anna.schumaker@netapp.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
/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