Hi all,
I've been assigned to work on the NVMe driver for this year's Google Summer of Code. It's a pleasure to be working with you all and I'm grateful that you have selected me.
The NVMe driver git repository can be found here: https://codeberg.org/ramenu/kolibrios-nvme-driver
So far, I've been working on the initialization portion of the driver and everything seems to be going well. Expect to see an agenda of the planned work to be done in the first half of GSoC in a few days. I need to do more research on what I can implement in the meantime.
I'll also post a checklist of all the planned to be implemented features and whatnot soon, just for the sake of tracking progress.
I look forward to working with all of you.
(GSoC 2024) NVMe Driver Implementation Status
Okay, so during the first half I'll primarily focus on finishing the initialization work, creation of the I/O queues and implementing some of the basic commands such as read, write, reset, to get it to a minimal working state and implement the API for the kernel to access the data on the disk. I'll post an attachment with the disk image as soon as it's complete (or just modify my Makefile to automatically add the driver to the image) so that it can be tested. Then, in the second phase, I can focus on fixing bugs and implementing more necessary features.
I will try my absolute best to make the driver compatible with all 1.x NVMe controllers, but I'm testing it solely on QEMU for now which uses 1.4, so if you have a older version unused NVMe SSD lying around, I would greatly appreciate it if you could test it to make sure it works on there as well. Obviously, I'm not responsible for any data loss or damage done, so please test at your own discretion.
I will try my absolute best to make the driver compatible with all 1.x NVMe controllers, but I'm testing it solely on QEMU for now which uses 1.4, so if you have a older version unused NVMe SSD lying around, I would greatly appreciate it if you could test it to make sure it works on there as well. Obviously, I'm not responsible for any data loss or damage done, so please test at your own discretion.
Who is online
Users browsing this forum: No registered users and 2 guests