Re: [PATCH 1/2] xfs: separate read-only variables in struct xfs_mount

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH 1/2] xfs: separate read-only variables in struct xfs_mount
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 12 May 2020 01:14:23 -0700
Cc: linux-xfs@xxxxxxxxxxxxxxx
In-reply-to: <20200512025949.1807131-2-david@fromorbit.com>
References: <20200512025949.1807131-1-david@fromorbit.com> <20200512025949.1807131-2-david@fromorbit.com>

I'm surprised the difference is that big.  The moves look obviously
fine, but why do you put the precalculated fields in the middle
of struct xfs_mount instead of at the end?

Follow-Ups:
- Re: [PATCH 1/2] xfs: separate read-only variables in struct xfs_mount
  - From: Dave Chinner

References:
- [PATCH 0/2] xfs: fix a couple of performance issues
  - From: Dave Chinner
- [PATCH 1/2] xfs: separate read-only variables in struct xfs_mount
  - From: Dave Chinner

Prev by Date: Re: [PATCH RFC] xfs: warn instead of fail verifier on empty attr3 leaf block
Next by Date: Re: [PATCH 2/2] xfs: convert m_active_trans counter to per-cpu
Previous by thread: [PATCH 1/2] xfs: separate read-only variables in struct xfs_mount
Next by thread: Re: [PATCH 1/2] xfs: separate read-only variables in struct xfs_mount
Index(es):
- Date
- Thread

[Index of Archives] [XFS Filesystem Development (older mail)] [Linux Filesystem Development] [Linux Audio Users] [Yosemite Trails] [Linux Kernel] [Linux RAID] [Linux SCSI]

Powered by Linux