All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] ltp-aiodio.part4: Run DIT000 with only 1 reader process
Date: Thu, 5 Jan 2023 16:38:06 +0100	[thread overview]
Message-ID: <Y7bu3jaL+nLIc/+0@pevik> (raw)
In-Reply-To: <20230105134416.15853-1-mdoucha@suse.cz>

Hi Martin,

> New changes in real-time kernel patchset give high priority to direct I/O
> readers and may cause writes to block indefinitely if there are too many
> reader processes running in parallel. Reduce the number of reader processes
> in DIT000 to 1 which was the dio_truncate default before rewrite to new API.

Correct, before 7a3741679d it was 1:

-int main(void)
+static void run(void)
 {
-	char filename[PATH_MAX];
-	int pid[NUM_CHILDREN];
-	int num_children = 1;
+	char *filename = "file";
+	int filesize = FILE_SIZE;
+	int num_children = NUM_CHILDREN;

> +++ b/runtest/ltp-aiodio.part4
> @@ -56,7 +56,7 @@ ADI007 dio_append
>  ADI008 dio_append
>  ADI009 dio_append
>  #Running dio_truncate
> -DIT000 dio_truncate
> +DIT000 dio_truncate -n 1
>  DIT001 dio_truncate
>  DIT002 dio_truncate
>  #Running dio_read

But I wonder why changing just the first dio_truncate will fix it
(obviously not). Could we detect RT and force -n 1 for it?
(utsname.version should have "PREEMPT RT"). Obviously only from version which
got affected.

Kind regards,
Petr


-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2023-01-05 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 13:44 [LTP] [PATCH] ltp-aiodio.part4: Run DIT000 with only 1 reader process Martin Doucha
2023-01-05 15:38 ` Petr Vorel [this message]
2023-01-05 16:27   ` Martin Doucha
2023-01-05 21:44     ` Petr Vorel

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=Y7bu3jaL+nLIc/+0@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    /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.