linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: "Darrick J. Wong" <djwong@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
	Chandan Babu R <chandan.babu@oracle.com>,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH 5/5] xfs: embedd struct xfbtree into the owning structure
Date: Fri, 5 Jan 2024 05:27:54 +0100	[thread overview]
Message-ID: <20240105042754.GA23630@lst.de> (raw)
In-Reply-To: <20240104192822.GI361584@frogsfrogsfrogs>

On Thu, Jan 04, 2024 at 11:28:22AM -0800, Darrick J. Wong wrote:
> Though looking at buftarg allocation and my old notes from a couple of
> years ago -- a second reason for allocating the buftarg during scrub
> setup was that the list_lru_init call allocates an array that's
> O(nodes_nr) and percpu_counter_init allocates an array that's
> O(maxcpus).  At the time I decided that it was better to put those large
> contiguous memory allocations in the ->setup routine where we don't have
> any vfs/xfs locks held, can run direct reclaim, and haven't done any xfs
> work yet.

Given that we use the page LRU for the shemfs pages, I don't think we
need the buftarg LRU list at all - aging just the buffer container
doesn't make much sense.

      reply	other threads:[~2024-01-05  4:27 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 20:38 RFC: in-memory btree simplifications Christoph Hellwig
2024-01-03 20:38 ` [PATCH 1/5] xfs: remove the in-memory btree header block Christoph Hellwig
2024-01-04  1:24   ` Darrick J. Wong
2024-01-04  6:27     ` Christoph Hellwig
2024-01-04 17:25       ` Darrick J. Wong
2024-01-03 20:38 ` [PATCH 2/5] xfs: remove struct xfboff_bitmap Christoph Hellwig
2024-01-03 20:38 ` [PATCH 3/5] xfs: remove bc_ino.flags Christoph Hellwig
2024-01-04  1:10   ` Darrick J. Wong
2024-01-03 20:38 ` [PATCH 4/5] xfs: factor out a xfs_btree_owner helper Christoph Hellwig
2024-01-04  1:14   ` Darrick J. Wong
2024-01-04  6:28     ` Christoph Hellwig
2024-01-03 20:38 ` [PATCH 5/5] xfs: embedd struct xfbtree into the owning structure Christoph Hellwig
2024-01-04  1:21   ` Darrick J. Wong
2024-01-04  6:32     ` Christoph Hellwig
2024-01-04  7:14       ` Darrick J. Wong
2024-01-04  7:17         ` Christoph Hellwig
2024-01-04  7:22           ` Darrick J. Wong
2024-01-04 19:28             ` Darrick J. Wong
2024-01-05  4:27               ` Christoph Hellwig [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=20240105042754.GA23630@lst.de \
    --to=hch@lst.de \
    --cc=chandan.babu@oracle.com \
    --cc=djwong@kernel.org \
    --cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).