From: "Florian-Ewald Müller" <florian-ewald.mueller@ionos.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Jack Wang <jinpu.wang@ionos.com>,
song@kernel.org, yukuai3@huawei.com, linux-raid@vger.kernel.org,
Neil Brown <neilb@suse.de>
Subject: Re: [PATCHv2] md: Replace md_thread's wait queue with the swait variant
Date: Tue, 5 Mar 2024 15:53:12 +0100 [thread overview]
Message-ID: <CAHJVUeijmJh2G+bqBXngC-2e4c9MmcoCK3SNUV2ofg1yZz2K2g@mail.gmail.com> (raw)
In-Reply-To: <CAHJVUehN_q8J96mtuq-DSmw2V4JVMcQ7GPROF2L-2GQTTH1RPQ@mail.gmail.com>
PS: backend devices were/are SSDs.
On Tue, Mar 5, 2024 at 3:52 PM Florian-Ewald Müller
<florian-ewald.mueller@ionos.com> wrote:
>
> Hi Paul,
>
> Regarding the IDLE state waiting:
> - yes, this could/should be backported to any version which already
> has swait_event_idle() macro(s) - and so also TASK_IDLE - defined.
>
> About our fio driven tests
> - we used fio "ini" files similar to:
>
> [global]
> description=Random Read/Write Access Pattern
> bssplit=512/8:1k/4:2k/4:4k/30:8k/20:16k/10:32k/8:64k/12:128k/4
> cpus_allowed=0-31
> cpus_allowed_policy=split
> numa_mem_policy=local
> fadvise_hint=0
> rw=randrw
> direct=1
> size=100%
> random_distribution=zipf:1.2
> percentage_random=80
> ioengine=libaio
> iodepth=128
> numjobs=1
> gtod_reduce=1
> group_reporting
> ramp_time=60
> runtime=300
> time_based
>
> [job0]
> filename=/dev/disk/by-name/vol0
>
> [job1]
> filename=/dev/disk/by-name/vol1
>
> ... and so on for >= 100 logical volumes.
>
> Best regards,
>
> On Tue, Mar 5, 2024 at 3:14 PM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
> >
> > Dear Florian-Ewald,
> >
> >
> > Thank you for your quick reply.
> >
> > Am 05.03.24 um 13:25 schrieb Florian-Ewald Müller:
> >
> > > Regarding the INTERRUPTIBLE wait:
> > > - it was introduced that time only for _not_ contributing to load-average.
> > > - now obsolete, see also explanation in our patch.
> >
> > Yes, I understood that. My question was regarding, if this should be
> > backported to the stable series.
> >
> > > Regarding our tests:
> > > - we used 100 logical volumes (and more) doing full-blown random rd/wr
> > > IO (fio) to the same md-raid1/raid5 device.
> >
> > Do you have a script to create these volumes and running the fio test,
> > so it’s easy to reproduce?
> >
> > Was it a spinning disk or SSD device?
> >
> >
> > Kind regards,
> >
> > Paul
prev parent reply other threads:[~2024-03-05 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 10:54 [PATCHv2] md: Replace md_thread's wait queue with the swait variant Jack Wang
2024-03-05 12:00 ` Paul Menzel
2024-03-05 12:25 ` Florian-Ewald Müller
2024-03-05 14:10 ` Paul Menzel
2024-03-05 14:52 ` Florian-Ewald Müller
2024-03-05 14:53 ` Florian-Ewald Müller [this message]
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=CAHJVUeijmJh2G+bqBXngC-2e4c9MmcoCK3SNUV2ofg1yZz2K2g@mail.gmail.com \
--to=florian-ewald.mueller@ionos.com \
--cc=jinpu.wang@ionos.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=pmenzel@molgen.mpg.de \
--cc=song@kernel.org \
--cc=yukuai3@huawei.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).