Util-Linux package development
 help / color / mirror / Atom feed
From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org,
	SCSI development list <linux-scsi@vger.kernel.org>,
	Douglas Gilbert <dgilbert@interlog.com>
Subject: Re: scsi_debug, iosize optimal < minimum (was: test sfdisk, optimal_iosize)
Date: Fri, 29 Jan 2016 17:18:20 +0100	[thread overview]
Message-ID: <201601291718.21185.sweet_f_a@gmx.de> (raw)
In-Reply-To: <201601291402.14306.sweet_f_a@gmx.de>

Hi,

I've noticed a possible problem with scsi_debug devices where
optimal_io_size < minimum_io_size.

The problem seems reproducable with kernel 4.4.0 and also with
stable version 4.1.15. For stable tree the last known working
version is 4.1.13.

How to reproduce:

uname -mr
modprobe -r scsi_debug 
modprobe scsi_debug dev_size_mb=100 sector_size=512
udevadm settle
devname=$(grep --with-filename scsi_debug /sys/block/*/device/model | awk -F '/' '{print $4}')
cat /sys/block/$devname/queue/{minimum_io_size,optimal_io_size}
modprobe -r scsi_debug


## output kernel 4.1.13 (openSUSE Leap):
4.1.13-5-default x86_64
512
32768


## output kernel 4.1.15 (openSUSE Leap):
4.1.15-8-default x86_64
512
64

cu,
Rudi

  reply	other threads:[~2016-01-29 16:18 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     ` Ruediger Meier [this message]
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

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=201601291718.21185.sweet_f_a@gmx.de \
    --to=sweet_f_a@gmx.de \
    --cc=dgilbert@interlog.com \
    --cc=kzak@redhat.com \
    --cc=linux-scsi@vger.kernel.org \
    --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