From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
"heming.zhao@suse.com" <heming.zhao@suse.com>
Subject: Re: [linux-lvm] [PATCH] tests: use correct RA size, underly dev & delay time.
Date: Thu, 13 Aug 2020 21:01:10 +0200 [thread overview]
Message-ID: <7568aefd-aa87-b549-4eb9-237acf02ab82@redhat.com> (raw)
In-Reply-To: <c86aeb1a-f7fd-000b-228d-e43029f25478@suse.com>
Dne 12. 08. 20 v 15:32 heming.zhao@suse.com napsal(a):
> a little more info about my patch.
> in one of my test env, system default read_ahead size is 1024 sector (512K),
> which bigger than 128k in test case. which causes _set_dev_node_read_ahead() to deny
> to set up RA.
>
Hi
Yeah - RA testing is a bit tricky - we had some issues whit systems
interfering with 'tuned' on RHEL which has been changing RA after
device creation.
We did same adaptation of other tests to handle multiple possible values.
I'll check what this test is doing.
Zdenek
prev parent reply other threads:[~2020-08-13 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 11:18 [linux-lvm] [PATCH] tests: use correct RA size, underly dev & delay time Zhao Heming
2020-08-12 13:32 ` heming.zhao
2020-08-13 19:01 ` Zdenek Kabelac [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=7568aefd-aa87-b549-4eb9-237acf02ab82@redhat.com \
--to=zkabelac@redhat.com \
--cc=heming.zhao@suse.com \
--cc=linux-lvm@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 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 NNTP newsgroup(s).