From: Krishna Kanth Reddy <krish.reddy@samsung.com>
To: axboe@kernel.dk
Cc: fio@vger.kernel.org
Subject: Re: [PATCH 0/1] Intoducing a new option max_latency_rw
Date: Fri, 12 Mar 2021 12:32:43 +0530 [thread overview]
Message-ID: <20210312070243.GA32222@test-zns> (raw)
In-Reply-To: <20210305054631.GA30850@test-zns>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
Hello Jens,
Just a gentle reminder.
Please review this patch and let us know if it looks fine or if it needs
some modification.
On Fri, Mar 05, 2021 at 11:16:31AM +0530, Krishna Kanth Reddy wrote:
>Hello Jens,
>Please review this patch and let us know if it looks fine or if it needs
>some modification.
>
>On Fri, Feb 12, 2021 at 04:00:44PM +0530, Krishna Kanth Reddy wrote:
>>The current max_latency option exits the FIO job, if latency of an I/O exceeds max_latency.
>>
>>For mixed workload if user wants to exit the FIO job only if latency
>>exceeds for a particular workload, i.e. either for read / write the support is not present.
>>
>>The new option max_latency_rw accepts read, write or mixed (Default) as option.
>>If user specifies read, the FIO job will exit only if read latency exceeds max_latency.
>>
>>Ankit Kumar (1):
>> Intoducing a new option max_latency_rw. The current max_latency option
>> exits the FIO job, if latency of an I/O exceeds max_latency.
>>
>>HOWTO | 17 +++++++++++++++++
>>cconv.c | 2 ++
>>fio.1 | 18 ++++++++++++++++++
>>init.c | 3 +++
>>io_u.c | 10 ++++++++--
>>options.c | 23 +++++++++++++++++++++++
>>thread_options.h | 8 ++++++++
>>7 files changed, 79 insertions(+), 2 deletions(-)
>>
>>--
>>2.30.0-rc0
>>
>>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2021-03-12 7:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210212103117epcas5p49dd1cc38a1590e2f007b90b0e708889d@epcas5p4.samsung.com>
2021-02-12 10:30 ` [PATCH 0/1] Intoducing a new option max_latency_rw Krishna Kanth Reddy
2021-02-12 10:30 ` [PATCH 1/1] Intoducing a new option max_latency_rw. The current max_latency option exits the FIO job, if latency of an I/O exceeds max_latency Krishna Kanth Reddy
2021-03-05 5:46 ` [PATCH 0/1] Intoducing a new option max_latency_rw Krishna Kanth Reddy
2021-03-12 7:02 ` Krishna Kanth Reddy [this message]
2021-03-12 14:30 ` Jens Axboe
[not found] <CGME20210212075335epcas5p1d9c49cbfc7fecc841010960bd8f93ff4@epcas5p1.samsung.com>
2021-02-12 7:53 ` Krishna Kanth Reddy
2021-02-26 9:52 ` Krishna Kanth Reddy
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=20210312070243.GA32222@test-zns \
--to=krish.reddy@samsung.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox