Hi Ranjit. I’m opening up this conversation to everyone by cc’ing the spdk mail list. Yes, the upcoming changes we have will complete the separation of dpdk and spdk. They will also abstract all of the posix dependencies (e.g. pthread_create becomes spdk_thread_create). The question about how many components to refactor needs to be agreed upon. At this point the feedback I’ve received from Ben and Daniel has been that they don’t want to convert all components at once. So I’ve been taking my pull requests apart into smaller pieces. Here is one of my older pull requests for reference. https://github.com/spdk/spdk/pull/132/commits <https://github.com/spdk/spdk/pull/132/commits> This can be compared with my current pull request: SPDK EAL Abstractions <https://github.com/spdk/spdk/pull/150> and with yours. Abstract and move rte_ functions into spdk functions that act ad pass-through functions in env_dpdk <https://github.com/spdk/spdk/pull/142> In terms of timeline, I’d like to complete these changes ASAP. If we can’t merge everything we have into master relatively soon (like this week) then I’d like to propose that a separate SPDK "platform_abstraction" branch be created (not a Github fork) so all of the environmental changes can be submitted there. This will allow contributors to develop these changes away from master more quickly, and the process of merging SHAs from the “platform_abstraction” into master can go more slowly. As was discussed at the Intel Builders conference last week, we should set up a periodic conference call to others in the community can discuss this and other subjects. I’ll work with Jim, Ben, and Daniel to set that up. John Meneghini john.a.meneghini(a)gmail.com