All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: zlang@kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] generic/095: add to the quick group
Date: Sun, 28 Apr 2024 01:49:53 +0800	[thread overview]
Message-ID: <20240427174953.nlw5gfi36syp5jnw@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com> (raw)
In-Reply-To: <20240427075530.1236045-1-hch@lst.de>

On Sat, Apr 27, 2024 at 09:55:30AM +0200, Christoph Hellwig wrote:
> generic/095 doesn't take more than 4 seconds on any of my test setups,

Yeah, it generally takes ~5 seconds. But there's a "LOAD_FACTOR", so
before we add it into quick group, I'd like to ask
do you think if it's worth increasing the default LOAD_FACTOR a bit to
give it more stress, or move it to quick group directly?

> but is exercises code that handles buffered write iterations interrupted
> by concurrent direct I/O that no other test in the quick group does.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
>  tests/generic/095 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/generic/095 b/tests/generic/095
> index 80448200b..9d0446e98 100755
> --- a/tests/generic/095
> +++ b/tests/generic/095
> @@ -7,7 +7,7 @@
>  # Concurrent mixed I/O (buffer I/O, aiodio, mmap, splice) on the same files
>  #
>  . ./common/preamble
> -_begin_fstest auto rw stress
> +_begin_fstest auto quick rw stress
>  
>  # Import common functions.
>  . ./common/filter
> -- 
> 2.39.2
> 
> 


  reply	other threads:[~2024-04-27 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-27  7:55 [PATCH] generic/095: add to the quick group Christoph Hellwig
2024-04-27 17:49 ` Zorro Lang [this message]
2024-04-29  4:38   ` Christoph Hellwig
2024-04-29 15:59   ` Darrick J. Wong
2024-04-29 18:53     ` Zorro Lang

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=20240427174953.nlw5gfi36syp5jnw@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com \
    --to=zlang@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=zlang@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.