From: "Darrick J. Wong" <djwong@kernel.org>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs@vger.kernel.org, aalbersh@kernel.org
Subject: Re: [PATCH 1/3] libxfs: change cache_node_allocate function signature
Date: Fri, 25 Sep 2026 15:56:34 -0700 [thread overview]
Message-ID: <20260925225634.GB2705364@frogsfrogsfrogs> (raw)
In-Reply-To: <20260925194535.397036-2-sandeen@redhat.com>
On Fri, Sep 25, 2026 at 02:41:43PM -0500, Eric Sandeen wrote:
> Modify cache_node_allocate() so that it returns a 0 / 1 status for
> cache miss / cache hit, with the cache node itself as a parameter. This
> will allow the next patches to properly differentiate underlying states
> and error conditions.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
I like this much better, thanks!
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> ---
> libxfs/cache.c | 26 +++++++++++++++++---------
> 1 file changed, 17 insertions(+), 9 deletions(-)
>
> diff --git a/libxfs/cache.c b/libxfs/cache.c
> index d5d9ba56..a6dabf92 100644
> --- a/libxfs/cache.c
> +++ b/libxfs/cache.c
> @@ -284,11 +284,14 @@ cache_shake(
> /*
> * Allocate a new hash node (updating atomic counter in the process),
> * unless doing so will push us over the maximum cache size.
> + * Return 1 with nodep set on success.
> + * Return 0 and NULL nodep otherwise (cache full, or alloc failure)
> */
> -static struct cache_node *
> +static int
> cache_node_allocate(
> struct cache * cache,
> - cache_key_t key)
> + cache_key_t key,
> + struct cache_node ** nodep)
> {
> unsigned int nodesfree;
> struct cache_node * node;
> @@ -302,21 +305,25 @@ cache_node_allocate(
> }
> cache->c_misses++;
> pthread_mutex_unlock(&cache->c_mutex);
> - if (!nodesfree)
> - return NULL;
> + if (!nodesfree) {
> + *nodep = NULL;
> + return 0;
> + }
> node = cache->alloc(key);
> if (node == NULL) { /* uh-oh */
> pthread_mutex_lock(&cache->c_mutex);
> cache->c_count--;
> pthread_mutex_unlock(&cache->c_mutex);
> - return NULL;
> + *nodep = NULL;
> + return 0;
> }
> pthread_mutex_init(&node->cn_mutex, NULL);
> list_head_init(&node->cn_mru);
> node->cn_count = 1;
> node->cn_priority = 0;
> node->cn_old_priority = -1;
> - return node;
> + *nodep = node;
> + return 1;
> }
>
> int
> @@ -366,8 +373,8 @@ __cache_node_purge(
> * hit, in which case this will all be over quickly and painlessly.
> * Otherwise, we allocate a new node, taking care not to expand the
> * cache beyond the requested maximum size (shrink it if it would).
> - * Returns one if hit in cache, otherwise zero. A node is _always_
> - * returned, however.
> + * Returns zero if hit in cache, one if a new node was allocated. A node
> + * is always returned.
> */
> int
> cache_node_get(
> @@ -457,9 +464,10 @@ next_object:
> /*
> * not found, allocate a new entry
> */
> - node = cache_node_allocate(cache, key);
> + cache_node_allocate(cache, key, &node);
> if (node)
> break;
> +
> priority = cache_shake(cache, priority, false);
> /*
> * We start at 0; if we free CACHE_SHAKE_COUNT we get
> --
> 2.55.0
>
>
next prev parent reply other threads:[~2026-09-25 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 19:41 [PATCH 0/3 V3] libxfs: better cache allocation error handling Eric Sandeen
2026-09-25 19:41 ` [PATCH 1/3] libxfs: change cache_node_allocate function signature Eric Sandeen
2026-09-25 22:56 ` Darrick J. Wong [this message]
2026-09-25 19:41 ` [PATCH 2/3] libxfs: Return -ENOMEM on actual cache node allocation failures Eric Sandeen
2026-09-25 22:58 ` Darrick J. Wong
2026-09-28 15:07 ` Eric Sandeen
2026-09-25 19:41 ` [PATCH 3/3] libxfs: do not allow cache growth to overflow Eric Sandeen
2026-09-25 22:59 ` Darrick J. Wong
2026-09-28 8:16 ` [PATCH 0/3 V3] libxfs: better cache allocation error handling Christoph Hellwig
2026-09-28 15:05 ` Eric Sandeen
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=20260925225634.GB2705364@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox