There's no reason why the virstor chunk size needs to relate to MAXPHYS.
Remove it. Instead, just make sure that the chunk size is a multiple of
the sector size.
Sponsored by: Dell EMC Isilon
Differential D45518
virstor: remove relation between chunk size and MAXPHYS rlibby on Jun 6 2024, 5:45 PM. Authored by Tags None Referenced Files
Subscribers
Details There's no reason why the virstor chunk size needs to relate to MAXPHYS. Sponsored by: Dell EMC Isilon New test in D45535 % sudo kyua debug -k /usr/tests/sys/Kyuafile geom/class/virstor/virstor_test:basic Executing command [ gvirstor label -v -s 64M -m 512 virstor.bjyhzA /dev/md0 ] Executing command [ gvirstor destroy virstor.bjyhzA ] Destroying test virstor device: virstor.bjyhzA Removing test memory disk: md0 geom/class/virstor/virstor_test:basic -> passed
Diff Detail
Event TimelineComment Actions I don't know this GEOM well enough to say whether this is right, but I can't see any reason it's wrong. It's unfortunate that there are no regression tests for this code.
Comment Actions I see there are tests for other geoms in tests/sys/geom, but I haven't figured out how to run them yet. Do you know? I might be able to cobble together something basic at least. Comment Actions Ah, I got it with sudo kyua test -k /usr/tests/sys/geom/Kyuafile They are not hooked up to the sys/Kyuafile. I wonder why. Comment Actions Hmm, they are on my system. When I run the full regression test suite I know for sure that the GEOM regression tests run. (The GELI ones in particular generate a ton of console output, so it's easy to see.) |