http://pkgs.fedoraproject.org/cgit/rpms/dpdk.git/tree/dpdk.spec
On 6 October 2017 at 20:17, Maxim Uvarov <maxim.uva...@linaro.org> wrote: > > > On 6 October 2017 at 20:05, Honnappa Nagarahalli < > honnappa.nagaraha...@linaro.org> wrote: > >> Any experts on how is the packaging done for DPDK? >> >> > ./pkg/dpdk.spec ? > > >> On 6 October 2017 at 08:36, Savolainen, Petri (Nokia - FI/Espoo) >> <petri.savolai...@nokia.com> wrote: >> >> > No, I'm pointing that the more there's common core SW, the more there >> >> > are trade-offs and the less direct HW access == less performance. >> For >> >> > optimal performance, the amount of common core SW is zero. >> >> >> >> Yes this is sort of the ideal but I doubt this type of installation >> >> will be accepted by e.g. Red Hat for inclusion in server-oriented >> >> Linux distributions. Jon Masters seems to be strongly against this >> >> (although I have only heard this second hand). So that's why I >> >> proposed the common (generic) core + platform specific drivers model >> >> that is used by e.g. Xorg and DPDK. Since DPDK is actually a user >> >> space framework (unlike Xorg), this should be a good model for ODP and >> >> something that Red Hat cannot object against. >> >> >> > >> > If every line of code is maintained properly, why a distro would care >> about the ratio between common core SW and HW specific driver SW? >> > >> > If they care, what is an acceptable ratio? Is it 90% common SW : 10% HW >> specific SW, 80:20, 50:50, 10:90 and why not 0:100? How this ratio should >> be calculated? >> > >> > DPDK is in Ubuntu already. Have anyone calculated what this ratio is >> for it? >> > >> > I'd be interested to see ODP as part of any distro first, and only >> after that speculate what other distros may or may not say. E.g. Ubuntu >> seem to accept packages that are only for single arch, e.g.: >> > librte-pmd-fm10k17.05 (= 17.05.2-0ubuntu1) [amd64, i386] <<< Intel Red >> Rock Canyon net driver, provided only for x86 >> > >> > -Petri >> > >> > >> > >
