From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: Re: scsi_debug, iosize optimal < minimum
Date: Thu, 4 Feb 2016 11:47:09 +0100 [thread overview]
Message-ID: <201602041147.09865.sweet_f_a@gmx.de> (raw)
In-Reply-To: <yq1a8nhlafo.fsf@sermon.lab.mkp.net>
On Wednesday 03 February 2016, Martin K. Petersen wrote:
> >>>>> "Ruediger" == Ruediger Meier <sweet_f_a@gmx.de> writes:
>
> Ruediger> In past (kernel<=4.1) optimal_io_size io size was 32768. Is
> Ruediger> this really correct now?
>
> We recently bumped the scsi_debug optimal I/O size to something akin
> to what real-world storage reports.
Regarding these kernel changes I've send a pull request via github to
fix the tests:
https://github.com/karelzak/util-linux/pull/272
cu,
Rudi
prev parent reply other threads:[~2016-02-04 10:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 10:31 test sfdisk, optimal_iosize Ruediger Meier
2016-01-29 11:31 ` Karel Zak
2016-01-29 11:52 ` Karel Zak
2016-01-29 13:02 ` Ruediger Meier
2016-01-29 16:18 ` scsi_debug, iosize optimal < minimum (was: test sfdisk, optimal_iosize) Ruediger Meier
2016-02-01 12:13 ` scsi_debug, iosize optimal < minimum Martin K. Petersen
2016-02-03 21:55 ` Ruediger Meier
2016-02-03 22:02 ` Martin K. Petersen
2016-02-04 10:47 ` Ruediger Meier [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=201602041147.09865.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--cc=util-linux@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