Perhaps someone from RedHat can comment? I suspect this is a kernel change, though.
On Sunday, November 21, 2021 at 6:31:39 PM UTC-8 alexi...@gmail.com wrote: > Hi, > > Looking into whether this is a bug, or an expect behavior with kernel 4.18+ > > RHEL 8.4 on AWS r5.xlarge hardware type, attaching nvme disks, observing > the nvme device is configuring optimal_io_size to 4KB > i.e. > /sys/devices/pci0000:00/0000:00:1c.0/nvme/nvme4/nvme4n1/queue/optimal_io_size > 4096 > > When attaching this device remotely using Linux-IO, the initiator device > is using the target's 'optimal_io_size' to set the max_sectors_kb. > i.e. > /sys/devices/platform/host1/session8/target1:0:0/1:0:0:0/block/sdb/queue/max_sectors_kb > > 4 > > This does not seem to be correct behavior. optimal_io_size and > max_sectors_kb should not be directly related. Do not observe this > behavior with RHEL7. > > target: > - RHEL 8.4, 4.18.0-305.12.1.el8_4.x86_64 > initiator: > - RHEL 8.4, 4.18.0-305.12.1.el8_4.x86_64 > - iscsi-initiator-utils-iscsiuio-6.2.1.2-1.gita8fcb37.el8.x86_64 > - iscsi-initiator-utils-6.2.1.2-1.gita8fcb37.el8.x86_64 > > > Thanks, > > Alexis. > > -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-iscsi+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/open-iscsi/49efbe97-d0ce-474e-9705-ffb690208e26n%40googlegroups.com.
