From: "Martin K. Petersen" <martin.petersen@oracle.com> To: Eric Wheeler <bcache@lists.ewheeler.net> Cc: Coly Li <colyli@suse.de>, linux-block@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>, Kent Overstreet <kent.overstreet@gmail.com>, "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>, "Martin K. Petersen" <martin.petersen@oracle.com> Subject: Re: [PATCH] bcache: make stripe_size configurable and persistent for hardware raid5/6 Date: Mon, 24 Jun 2019 19:24:44 -0400 [thread overview] Message-ID: <yq17e9ao9c3.fsf@oracle.com> (raw) In-Reply-To: <alpine.LRH.2.11.1906241800350.1114@mx.ewheeler.net> (Eric Wheeler's message of "Mon, 24 Jun 2019 18:14:59 +0000 (UTC)") Eric, > Perhaps they do not set stripe_width using io_opt? I did a grep to see > if any of them did, but I didn't see them. How is stripe_width > indicated by RAID controllers? The values are reported in the Block Limits VPD page for each SCSI block device and are thus set by the SCSI disk driver. IOW, the RAID controller device drivers have nothing to do with this. For RAID controllers specifically, the controller firmware will fill out the VPD fields for each virtual SCSI disk when you configure a RAID set. For pretty much everything else, the Block Limits come straight from the device itself. Also note that these values aren't specific to RAID controllers at all. Most new SCSI devices, including disk drives and SSDs, will fill out the Block Limits VPD page one way or the other. Even some USB storage devices are providing this page. > If they do set io_opt, then at least my Areca 1883 does not set io_opt > as of 4.19.x. I also have a LSI MegaRAID 3108 which does not report > io_opt as of 4.1.x, but that is an older kernel so maybe support has > been added since then. I have several MegaRAIDs that all report it. But it depends on the controller firmware. > Is it visible through sysfs or debugfs so I can check my hardware > support without hacking debugging the kernel? To print the block device topology: # lsblk -t or look up io_opt in sysfs: # grep . /sys/block/sdX/queue/optimal_io_size You can also query a SCSI device's Block Limits directly: # sg_vpd -p bl /dev/sdX If you want to tinker, you can simulate a SCSI disk with your choice of io_opt: # modprobe scsi_debug opt_blks=N where N is the number of logical blocks to report as being the optimal I/O size. -- Martin K. Petersen Oracle Linux Engineering
WARNING: multiple messages have this Message-ID (diff)
From: "Martin K. Petersen" <martin.petersen@oracle.com> To: Eric Wheeler <bcache@lists.ewheeler.net> Cc: Coly Li <colyli@suse.de>, linux-block@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>, Kent Overstreet <kent.overstreet@gmail.com>, "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>, "Martin K. Petersen" <martin.petersen@oracle.com> Subject: Re: [PATCH] bcache: make stripe_size configurable and persistent for hardware raid5/6 Date: Mon, 24 Jun 2019 19:24:44 -0400 [thread overview] Message-ID: <yq17e9ao9c3.fsf@oracle.com> (raw) In-Reply-To: <alpine.LRH.2.11.1906241800350.1114@mx.ewheeler.net> (Eric Wheeler's message of "Mon, 24 Jun 2019 18:14:59 +0000 (UTC)") Eric, > Perhaps they do not set stripe_width using io_opt? I did a grep to see > if any of them did, but I didn't see them. How is stripe_width > indicated by RAID controllers? The values are reported in the Block Limits VPD page for each SCSI block device and are thus set by the SCSI disk driver. IOW, the RAID controller device drivers have nothing to do with this. For RAID controllers specifically, the controller firmware will fill out the VPD fields for each virtual SCSI disk when you configure a RAID set. For pretty much everything else, the Block Limits come straight from the device itself. Also note that these values aren't specific to RAID controllers at all. Most new SCSI devices, including disk drives and SSDs, will fill out the Block Limits VPD page one way or the other. Even some USB storage devices are providing this page. > If they do set io_opt, then at least my Areca 1883 does not set io_opt > as of 4.19.x. I also have a LSI MegaRAID 3108 which does not report > io_opt as of 4.1.x, but that is an older kernel so maybe support has > been added since then. I have several MegaRAIDs that all report it. But it depends on the controller firmware. > Is it visible through sysfs or debugfs so I can check my hardware > support without hacking debugging the kernel? To print the block device topology: # lsblk -t or look up io_opt in sysfs: # grep . /sys/block/sdX/queue/optimal_io_size You can also query a SCSI device's Block Limits directly: # sg_vpd -p bl /dev/sdX If you want to tinker, you can simulate a SCSI disk with your choice of io_opt: # modprobe scsi_debug opt_blks=N where N is the number of logical blocks to report as being the optimal I/O size. -- Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-06-24 23:25 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 [this message] 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
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=yq17e9ao9c3.fsf@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: linkBe 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.