All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Pankaj Raghav <p.raghav@samsung.com>,
	Dave Chinner <david@fromorbit.com>,
	"Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>
Cc: zlang@redhat.com, fstests@vger.kernel.org, djwong@kernel.org,
	mcgrof@kernel.org, gost.dev@samsung.com,
	linux-xfs@vger.kernel.org
Subject: Re: [PATCH 0/2] fstest changes for LBS
Date: Tue, 23 Jan 2024 21:05:36 +0530	[thread overview]
Message-ID: <87le8gjc53.fsf@doe.com> (raw)
In-Reply-To: <69e73772-80e2-4cfe-a95d-d680d7686e3c@samsung.com>

Pankaj Raghav <p.raghav@samsung.com> writes:

> On 23/01/2024 01:25, Dave Chinner wrote:
>> On Mon, Jan 22, 2024 at 12:17:49PM +0100, Pankaj Raghav (Samsung) wrote:
>>> From: Pankaj Raghav <p.raghav@samsung.com>
>>>
>>> Some tests need to be adapted to for LBS[1] based on the filesystem
>>> blocksize. These are generic changes where it uses the filesystem
>>> blocksize instead of assuming it.
>>>
>>> There are some more generic test cases that are failing due to logdev
>>> size requirement that changes with filesystem blocksize. I will address
>>> them in a separate series.
>>>
>>> [1] https://lore.kernel.org/lkml/20230915183848.1018717-1-kernel@pankajraghav.com/
>>>
>>> Pankaj Raghav (2):
>>>   xfs/558: scale blk IO size based on the filesystem blksz
>>>   xfs/161: adapt the test case for LBS filesystem
>> 
>> Do either of these fail and require fixing for a 64k page size
>> system running 64kB block size?
>> 
>> i.e. are these actual 64kB block size issues, or just issues with
>> the LBS patchset?
>> 
>
> I had the same question in mind. Unfortunately, I don't have access to any 64k Page size
> machine at the moment. I will ask around if I can get access to it.
>
> @Zorro I saw you posted a test report for 64k blocksize. Is it possible for you to
> see if these test cases(xfs/161, xfs/558) work in your setup with 64k block size?
>
> CCing Ritesh as I saw him post a patch to fix a testcase for 64k block size.

Hi Pankaj,

So I tested this on Linux 6.6 on Power8 qemu (which I had it handy).
xfs/558 passed with both 64k blocksize & with 4k blocksize on a 64k
pagesize system.
However, since on this system the quota was v4.05, it does not support
bigtime feature hence could not run xfs/161. 

xfs/161       [not run] quota: bigtime support not detected
xfs/558 7s ...  21s

I will collect this info on a different system with latest kernel and
will update for xfs/161 too.

-ritesh

  parent reply	other threads:[~2024-01-23 15:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 11:17 [PATCH 0/2] fstest changes for LBS Pankaj Raghav (Samsung)
2024-01-22 11:17 ` [PATCH 1/2] xfs/558: scale blk IO size based on the filesystem blksz Pankaj Raghav (Samsung)
2024-01-22 16:53   ` Darrick J. Wong
2024-01-22 17:23     ` Pankaj Raghav
2024-03-13 20:08       ` Darrick J. Wong
2024-01-22 11:17 ` [PATCH 2/2] xfs/161: adapt the test case for LBS filesystem Pankaj Raghav (Samsung)
2024-01-22 16:57   ` Darrick J. Wong
2024-01-22 17:32     ` Pankaj Raghav
2024-01-25 16:06     ` Pankaj Raghav
2024-01-23  0:25 ` [PATCH 0/2] fstest changes for LBS Dave Chinner
2024-01-23  8:52   ` Pankaj Raghav
2024-01-23 13:43     ` Zorro Lang
2024-01-23 15:39       ` Ritesh Harjani
2024-01-23 16:33       ` Pankaj Raghav
2024-01-23 15:35     ` Ritesh Harjani [this message]
2024-01-23 16:40       ` Pankaj Raghav
2024-01-23 19:42         ` Ritesh Harjani
2024-01-23 20:21           ` Pankaj Raghav
2024-01-24 16:58             ` Darrick J. Wong
2024-01-24 21:06               ` Pankaj Raghav

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=87le8gjc53.fsf@doe.com \
    --to=ritesh.list@gmail.com \
    --cc=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=gost.dev@samsung.com \
    --cc=kernel@pankajraghav.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=zlang@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 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.