[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <666408.1647614889@warthog.procyon.org.uk>
Date: Fri, 18 Mar 2022 14:48:09 +0000
From: David Howells <dhowells@...hat.com>
To: Jeff Layton <jlayton@...nel.org>
Cc: dhowells@...hat.com, linux-cachefs@...hat.com,
Anna Schumaker <anna.schumaker@...app.com>,
Steve French <sfrench@...ba.org>,
Dominique Martinet <asmadeus@...ewreck.org>,
David Wysochanski <dwysocha@...hat.com>,
Ilya Dryomov <idryomov@...il.com>,
Jeffle Xu <jefflexu@...ux.alibaba.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-afs@...ts.infradead.org, linux-nfs@...r.kernel.org,
linux-cifs@...r.kernel.org, ceph-devel@...r.kernel.org,
v9fs-developer@...ts.sourceforge.net,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v4 13/20] netfs: Add a netfs inode context
Jeff Layton <jlayton@...nel.org> wrote:
> > +static inline bool netfs_is_cache_enabled(struct netfs_i_context *ctx)
> > +{
> > +#if IS_ENABLED(CONFIG_FSCACHE)
> > + struct fscache_cookie *cookie = ctx->cache;
> > +
> > + return fscache_cookie_valid(cookie) && cookie->cache_priv &&
> > + fscache_cookie_enabled(cookie);
>
>
> As you mentioned in the other thread, it may be cleaner to move the
> cookie->cache_priv check into fscache_cookie_enabled. Is there ever a
> case where you'd need to separate the two checks?
I'm not sure, but I'd prefer not to do it in this series as it would affect
NFS plus some other operations, so will need retesting thoroughly. I'd prefer
to defer it.
David
Powered by blists - more mailing lists