From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Eric Wheeler <bcache@lists.ewheeler.net>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Kent Overstreet <kent.overstreet@gmail.com>,
Coly Li <colyli@suse.de>,
linux-block@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
"open list:BCACHE (BLOCK LAYER CACHE)"
<linux-bcache@vger.kernel.org>
Subject: Re: [PATCH] bcache: make stripe_size configurable and persistent for hardware raid5/6
Date: Mon, 10 Jan 2022 21:55:21 -0500 [thread overview]
Message-ID: <yq1fspvq99j.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <611f98fc-222-8dd2-6b81-d570fb91fc@ewheeler.net> (Eric Wheeler's message of "Mon, 10 Jan 2022 15:30:24 -0800 (PST)")
Eric,
> Do you know if io_opt can be configured on scsi devices that do not
> have io_opt provided by the controller? If so, or if it would be easy
> to add, then configuring io_opt at the scsi layer is probably a better
> option so subsystems besides bcache would benefit.
There is currently no way to do this in the SCSI sysfs interface.
However, io_opt is a queue_limits parameter. The appropriate location
for modification is blk-sysfs.c. We already allow overriding other block
device properties such as rotational, stable_writes, discards, max I/O
size, etc. I don't see any particular reason why we couldn't also permit
overriding the optimal I/O size.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2022-01-11 2:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d3f7fd44-9287-c7fa-ee95-c3b8a4d56c93@suse.de>
2019-06-22 23:16 ` [PATCH] bcache: make stripe_size configurable and persistent for hardware raid5/6 Eric Wheeler
2019-06-22 23:16 ` Eric Wheeler
2019-06-23 0:41 ` Martin K. Petersen
2019-06-23 0:41 ` Martin K. Petersen
2019-06-24 6:57 ` Coly Li
2019-06-24 7:05 ` Coly Li
2019-06-24 18:14 ` Eric Wheeler
2019-06-24 23:24 ` Martin K. Petersen
2019-06-24 23:24 ` Martin K. Petersen
2019-06-26 0:23 ` Eric Wheeler
2019-06-26 0:23 ` Eric Wheeler
2019-06-26 2:50 ` Martin K. Petersen
2019-06-26 2:50 ` Martin K. Petersen
2019-06-25 1:59 ` Coly Li
2022-01-06 3:29 ` Eric Wheeler
2022-01-06 16:17 ` Coly Li
2022-01-08 0:21 ` Martin K. Petersen
2022-01-08 4:54 ` Eric Wheeler
2022-01-08 21:51 ` Eric Wheeler
2022-01-10 16:14 ` Martin K. Petersen
2022-01-10 23:30 ` Eric Wheeler
2022-01-11 2:55 ` Martin K. Petersen [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=yq1fspvq99j.fsf@ca-mkp.ca.oracle.com \
--to=martin.petersen@oracle.com \
--cc=bcache@lists.ewheeler.net \
--cc=colyli@suse.de \
--cc=corbet@lwn.net \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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 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.