05/02/2021 10:38, Bruce Richardson: > On Fri, Feb 05, 2021 at 09:26:05AM +0000, Juraj Linkeš wrote: > > From: Bruce Richardson <bruce.richard...@intel.com> > > > The block for cross-compiling is fairly large and complex, so I'm > > > wondering how > > > we can simplify things a bit. If we had multiple kernel modules I'd > > > suggest > > > splitting thing up into a native and cross-build subdirectories to get > > > the build > > > info, but that seems like overkill here. > > > > This configuration would be the same for all kernel modules (right?), so > > I'm not sure how the number of kernel modules is relevant here. > > If we split it, what would the dir structure look like? Something like this? > > kernel/linux/ > > ├── aarch64 > > ├── native > > ├── kni > > ├── <other_mods> > > > > Yep, that would be the structure - though perhaps with "cross" rather than > "aarch64" being the alternative to "native". The reason I felt that the > number of kmods was relevant is that it would be really weird to have 2 > subdirectories for infrastructure for a single directory containing one > module - a 200% percent overhead ratio. :-) Therefore, I thinking keeping > it all in one file is best, but we'll see after the next revision how it > looks.
Going forward, we should not have any Linux kernel module in this DPDK repository. We must encourage upstream developments. That's why I am against adding more directories in kernel/linux/. KNI is still there (could move later), but please handle it in kni/ directory.
