Kernel version question
-
This is probably a child's play for some of you guys!
I'm looking to find out from what stable release of the kernel these changes are in the source:
https://github.com/torvalds/linux/commit/13880f5b57adf34d050cf7e229a6326da45a7347
I'm not familiar with github so I just don't understand how or where I can find this info.It's for SR-IOV support for NVMe drives.
-
Well the tag is for:
https://github.com/torvalds/linux/releases/tag/v4.19-rc4That's in the latest release candidate, so there is no stable with this yet.
If you're daring, you can pull the driver out of this release and compile it with the 4.18 release.
-
@tonyshowoff said in Kernel version question:
Well the tag is for:
https://github.com/torvalds/linux/releases/tag/v4.19-rc4That's in the latest release candidate, so there is no stable with this yet.
If you're daring, you can pull the driver out of this release and compile it with the 4.18 release.
But it also says:
keithbusch authored and axboe committed on Jun 20, 2016
That's more than two years ago. If the change was made that long ago it cannot be just in the latest non-released kernel, can it?
-
@pete-s said in Kernel version question:
@tonyshowoff said in Kernel version question:
Well the tag is for:
https://github.com/torvalds/linux/releases/tag/v4.19-rc4That's in the latest release candidate, so there is no stable with this yet.
If you're daring, you can pull the driver out of this release and compile it with the 4.18 release.
But it also says:
keithbusch authored and axboe committed on Jun 20, 2016
That's more than two years ago. If the change was made that long ago it cannot be just in the latest non-released kernel, can it?
Might not have been included until now.
-
Alright, I took another approach at this.
Looking directly at the source for different kernels over at kernel.org I can see that the NVMe driver has SR-IOV support from kernel version 4.8.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/drivers/nvme/host/pci.c?h=v4.8#n2015It's very interesting for virtualized workloads because SR-IOV means you can assign the NVMe disk to different VMs directly and bypass the hypervisor. This is the same for NICs at 10/25/40/100 gigabit. There will be a significant performance drop if you don't use SR-IOV.
