From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] read_all: scale down how many times we read by default
Date: Tue, 9 Jun 2020 09:33:23 -0400 (EDT) [thread overview]
Message-ID: <1521498136.15325724.1591709603454.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <877dwgxv96.fsf@our.domain.is.not.set>
----- Original Message -----
> OK this makes sense. We shouldn't be stress testing the system in this
> runtest file.
Pushed.
prev parent reply other threads:[~2020-06-09 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 10:55 [LTP] [PATCH] read_all: scale down how many times we read by default Jan Stancek
2020-06-09 12:27 ` Li Wang
2020-06-09 12:45 ` Richard Palethorpe
2020-06-09 13:33 ` Jan Stancek [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=1521498136.15325724.1591709603454.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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.