vdo
vdo copied to clipboard
dm-vdo
Status of upstreaming
Hello,
I regularly check vdo-devel and here, but I see not report of advance towards upstreaming of VDO to the mainline Kernel.
- Is it still a goal?
- What is missing for getting VDO ready for upstream?
- Do you have an estimated ETA ?
- Where would be the place to follow the upstreaming effort advances?
Thanks
Hi @sheepdestroyer
Hello,
I regularly check vdo-devel and here, but I see not report of advance towards upstreaming of VDO to the mainline Kernel.
- Is it still a goal?
Yes, very much so.
- What is missing for getting VDO ready for upstream?
We are still working towards making our code acceptable to conform to the standards of the kernel community in terms of code formatting and structure. We are also still working through some issues to make sure we behave as a DM target the way that the DM community/subsystem expects us to work.
- Do you have an estimated ETA ?
Not an official date, but hopefully in the next few months, we are expecting to put out our RFC to the relevant mailing lists.
- Where would be the place to follow the upstreaming effort advances?
The best place to look is at the 'unstable' branch on the vdo and kvdo projects here on github. That is where we publish our upstream-candidate code and all of the changes as they are made. We typically update that every 1-2 weeks, but sometimes there can be delays due to other circumstances (Holidays, etc.) It should be noted that the 'kvdo' project is the place to find what is going to eventually be included in the RFC. The 'vdo' project is intended to deliver usermode functionality and does not contain the full extent of the Upstreaming task at hand.
Hi @guzenkov, we have made significant progress since the last update. We have submitted the code for review to the dm-devel mailing list [0], and we're working through the feedback that we're receiving [1].
[0] https://lore.kernel.org/dm-devel/[email protected]/ [1] https://lore.kernel.org/dm-devel/?q=dm-vdo