mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Daniel Wagner <dwagner@suse.de>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	Shin'ichiro Kawasaki <shinichiro@fastmail.com>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: [PATCH blktests v3 04/12] common/xfs: Limit fio size job to fit into xfs fs
Date: Wed, 3 May 2023 09:29:04 +0000	[thread overview]
Message-ID: <74e9c631-23cd-705c-7043-88f345598ad1@nvidia.com> (raw)
In-Reply-To: <20230503080258.14525-5-dwagner@suse.de>

On 5/3/23 01:02, Daniel Wagner wrote:
> The usable capacity of the filesystem is less than the raw
> partition/device size due to the additional meta/log data.
>
> Ensure that the job size for fio is not exceeding the limits.
>
> Because we have hard coded the path where we mount the filesystem
> and don't want to expose this, we just update max size inside
> _xfs_run_fio_verify_io(). No need to leak this into the caller.
>
> Signed-off-by: Daniel Wagner <dwagner@suse.de>
> ---
>   common/xfs | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/common/xfs b/common/xfs
> index 413c2820ffaf..37ce85878df2 100644
> --- a/common/xfs
> +++ b/common/xfs
> @@ -37,6 +37,9 @@ _xfs_run_fio_verify_io() {
>   		sz_mb="${avail_mb}"
>   	else
>   		sz_mb="$(convert_to_mb "${sz}")"
> +		if [[ "${sz_mb}" -gt "${avail_mb}" ]]; then
> +			sz_mb="${avail_mb}"
> +		fi
>   	fi
>   
>   	_run_fio_verify_io --size="${sz_mb}m" --directory="${mount_dir}/"


this is exactly how it should to start with, the only
is now we are silently reducing the fio job size maybe that is okay ?

or we should error out here instead of being smart ?

-ck



  reply	other threads:[~2023-05-03  9:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03  8:02 [PATCH blktests v3 00/12] nvme testsuite runtime optimization Daniel Wagner
2023-05-03  8:02 ` [PATCH blktests v3 01/12] nvme/rc: Auto convert test device size info Daniel Wagner
2023-05-03  9:22   ` Chaitanya Kulkarni
2023-05-03  9:26     ` Daniel Wagner
2023-05-07 22:49   ` Shinichiro Kawasaki
2023-05-03  8:02 ` [PATCH blktests v3 02/12] nvme: Do not hard code device size for dd test Daniel Wagner
2023-05-03  9:23   ` Chaitanya Kulkarni
2023-05-07 22:51   ` Shinichiro Kawasaki
2023-05-03  8:02 ` [PATCH blktests v3 03/12] common/xfs: Make size argument optional for _xfs_run_fio_verify_io Daniel Wagner
2023-05-03  9:25   ` Chaitanya Kulkarni
2023-05-03  8:02 ` [PATCH blktests v3 04/12] common/xfs: Limit fio size job to fit into xfs fs Daniel Wagner
2023-05-03  9:29   ` Chaitanya Kulkarni [this message]
2023-05-03  9:42     ` Daniel Wagner
2023-05-03  8:02 ` [PATCH blktests v3 05/12] nvme: Use runtime fio background jobs Daniel Wagner
2023-05-07 22:56   ` Shinichiro Kawasaki
2023-05-03  8:02 ` [PATCH blktests v3 06/12] Documentation: Add info on nvme_tr_type Daniel Wagner
2023-05-03  9:32   ` Chaitanya Kulkarni
2023-05-07 23:21   ` Shinichiro Kawasaki
2023-05-03  8:02 ` [PATCH blktests v3 07/12] nvme: Make test image size configurable Daniel Wagner
2023-05-03  9:32   ` Chaitanya Kulkarni
2023-05-07 23:09   ` Shinichiro Kawasaki
2023-05-03  8:02 ` [PATCH blktests v3 08/12] nvme/rc: Add minimal test image size requirement Daniel Wagner
2023-05-03  9:35   ` Chaitanya Kulkarni
2023-05-07 23:19   ` Shinichiro Kawasaki
2023-05-03  8:02 ` [PATCH blktests v3 09/12] common/fio: Limit number of random jobs Daniel Wagner
2023-05-03  9:41   ` Chaitanya Kulkarni
2023-05-03 11:01     ` Daniel Wagner
2023-05-04  5:16       ` Chaitanya Kulkarni
2023-05-04  6:07         ` Daniel Wagner
2023-05-03  8:02 ` [PATCH blktests v3 10/12] nvme/rc: Calculate IO size for random fio jobs Daniel Wagner
2023-05-07 23:31   ` Shinichiro Kawasaki
2023-05-10 17:14     ` Daniel Wagner
2023-05-03  8:02 ` [PATCH blktests v3 11/12] nvme/rc: Move discovery generation counter code to rc Daniel Wagner
2023-05-07 23:34   ` Shinichiro Kawasaki
2023-05-10 17:24     ` Daniel Wagner
2023-05-11 16:44       ` Shinichiro Kawasaki
2023-05-03  8:02 ` [PATCH blktests v3 12/12] nvme: Make the number iterations configurable Daniel Wagner
2023-05-03  9:45   ` Chaitanya Kulkarni

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=74e9c631-23cd-705c-7043-88f345598ad1@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=dwagner@suse.de \
    --cc=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=shinichiro@fastmail.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

all inboxes | Powered by JetHome®