All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Carlos Maiolino <cem@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>,
	Dave Chinner <david@fromorbit.com>,
	linux-xfs@vger.kernel.org, djwong@kernel.org
Subject: Re: [PATCH 1/2] xfs: replace iclogs circular list with a list_head
Date: Wed, 25 Jun 2025 08:21:57 +0200	[thread overview]
Message-ID: <20250625062157.GA9641@lst.de> (raw)
In-Reply-To: <b5q3uuhkn2jqcjgg6qcv6z444bftoec7dwxh4qoxbj64z2vnfv@gogvtu75o4qj>

On Tue, Jun 24, 2025 at 08:17:05PM +0200, Carlos Maiolino wrote:
> > 	struct xlog {
> > 		...
> > 		struct xlog_in_core	*l_iclog;
> > 		struct xlog_in_core	*l_iclogs[XLOG_MAX_ICLOGS];
> > 	};
> 
> 	Thanks for the tip hch, but wouldn't this break the mount option? So far
> 	the user can specify how many iclogs will be in memory, by allocating
> 	a fixed array, we essentially lock it to 8 iclogs, no?
> 
> Cheers, and thanks again for the review.

Well, if you look at the helper I whiteboard coded below it only walks
the array until the number of specified.  As long as the maximum numbers
of iclogs is relatively slow and/or the default is close to the maximum
this seems optimal.  If we every support a very huge number or default
to something much lower than the default a separate allocation would
be better here, but that's a trivial change.


  reply	other threads:[~2025-06-25  6:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20  7:07 [PATCH 0/2] xfs: iclog small cleanup cem
2025-06-20  7:07 ` [PATCH 1/2] xfs: replace iclogs circular list with a list_head cem
2025-06-24  2:16   ` Dave Chinner
2025-06-24  4:43     ` Carlos Maiolino
2025-06-24 13:57     ` Christoph Hellwig
2025-06-24 18:17       ` Carlos Maiolino
2025-06-25  6:21         ` Christoph Hellwig [this message]
2025-06-25  8:20           ` Carlos Maiolino
2025-06-25 11:22             ` Christoph Hellwig
2025-06-20  7:08 ` [PATCH 2/2] xfs: kill xlog_in_core_2_t typedef cem
2025-06-24 13:59   ` Christoph Hellwig
2025-06-25  8:21     ` Carlos Maiolino

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=20250625062157.GA9641@lst.de \
    --to=hch@lst.de \
    --cc=cem@kernel.org \
    --cc=david@fromorbit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.