Re: release schedule change proposal

[Luca Boccassi]

On Mon, 2021-11-15 at 15:58 +0100, Thomas Monjalon wrote:
> For the last 5 years, DPDK was doing 4 releases per year,
> in February, May, August and November (the LTS one):
>   .02   .05   .08   .11 (LTS)
> 
> This schedule has multiple issues:
>   - clash with China's Spring Festival
>   - too many rushes, impacting maintainers & testers
>   - not much buffer, impacting proposal period
> 
> I propose to switch to a new schedule with 3 releases per year:
>   .03  .07  .11 (LTS)
> 
> New LTS branch would start at the same time of the year as before.
> There would be one less intermediate release during spring/summer:
> .05 and .08 intermediate releases would become a single .07.
> I think it has almost no impact for the users.
> This change could be done starting next year.
> 
> In details, this is how we could extend some milestones:
> 
>   ideal schedule so far (in 13 weeks):
>   proposal deadline: 4
>   rc1 - API freeze: 5
>   rc2 - PMD features freeze: 2
>   rc3 - app features freeze: 1
>   rc4 - last chance to fix: 1
>   release: 0
> 
>   proposed schedule (in 17 weeks):
>   proposal deadline: 4
>   rc1 - API freeze: 7
>   rc2 - PMD features freeze: 3
>   rc3 - app features freeze: 1
>   rc4 - more fixes: 1
>   rc5 - last chance buffer: 1
>   release: 0
> 
> Opinions?

We upload only LTS releases to Debian/Ubuntu, so as long as those stay
the same as it is proposed here, no problem for us.

-- 
Kind regards,
Luca Boccassi

Re: [dpdk-users] A compilation problem on arm64

[Luca Boccassi]

On Mon, 2021-01-18 at 09:40 +0100, David Marchand wrote:
> On Sun, Jan 17, 2021 at 11:04 PM LemmyHuang  wrote:
> > Dear Concerns,
> > 
> > 
> > I have a compilation problem on arm64.
> > My environment is dpdk-19.11, gcc-9.3.1 and kernel-5.10.0-0.0.0.7.aarch64. 
> > The errors are as follows:
> > 
> > 
> >  ...
> >  CC [M] 
> > /home/abuild/rpmbuild/BUILD/dpdk-19.11/arm64-armv8a-linux-gcc/build/kernel/linux/kni/kni_misc.o
> >  [0m
> >  CC [M] 
> > /home/abuild/rpmbuild/BUILD/dpdk-19.11/arm64-armv8a-linux-gcc/build/kernel/linux/kni/kni_net.o
> >  [0m
> >  LD librte_common_octeontx2.so.20.0 [0m
> >  INSTALL-LIB librte_common_octeontx2.so.20.0 [0m
> >  == Build drivers/bus [0m
> >  In file included from ./include/linux/atomic.h:7, [0m
> >  from 
> > ./include/asm-generic/bitops/atomic.h:5, [0m
> >  from 
> > ./arch/arm64/include/asm/bitops.h:26, [0m
> >  from 
> > ./include/linux/bitops.h:29, [0m
> >  from 
> > ./include/linux/kernel.h:12, [0m
> >  from 
> > ./include/linux/list.h:9, [0m
> >  from 
> > ./include/linux/rculist.h:10, [0m
> >  from 
> > ./include/linux/pid.h:5, [0m
> >  from 
> > ./include/linux/sched.h:14, [0m
> >  from 
> > ./include/linux/ratelimit.h:6, [0m
> >  from 
> > ./include/linux/dev_printk.h:16, [0m
> >  from 
> > ./include/linux/device.h:15, [0m
> >  from 
> > /home/abuild/rpmbuild/BUILD/dpdk-19.11/arm64-armv8a-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:8:
> >  [0m
> >  ./include/linux/atomic-arch-fallback.h: In function 
> > 'igbuio_pci_open': [0m
> >  ./arch/arm64/include/asm/atomic.h:20:20: error: inlining failed in 
> > call to 'arch_atomic_sub.constprop': --param max-inline-insns-single-O2 
> > limit reached [-Werror=inline] [0m
> >   20 | static inline void arch_##op(int i, atomic_t 
> > *v) \ [0m
> >| 
> >  ^ [0m
> >  ./arch/arm64/include/asm/atomic.h:30:1: note: in expansion of 
> > macro 'ATOMIC_OP' [0m
> >   30 | ATOMIC_OP(atomic_sub) [0m
> >| ^ [0m
> >  In file included from ./include/linux/atomic.h:81, [0m
> >  from 
> > ./include/asm-generic/bitops/atomic.h:5, [0m
> >  from 
> > ./arch/arm64/include/asm/bitops.h:26, [0m
> >  from 
> > ./include/linux/bitops.h:29, [0m
> >  from 
> > ./include/linux/kernel.h:12, [0m
> >  from 
> > ./include/linux/list.h:9, [0m
> >  from 
> > ./include/linux/rculist.h:10, [0m
> >  from 
> > ./include/linux/pid.h:5, [0m
> >  from 
> > ./include/linux/sched.h:14, [0m
> >  from 
> > ./include/linux/ratelimit.h:6, [0m
> >  from 
> > ./include/linux/dev_printk.h:16, [0m
> >  from 
> > ./include/linux/device.h:15, [0m
> >  from 
> > /home/abuild/rpmbuild/BUILD/dpdk-19.11/arm64-armv8a-linux-gcc/build/kernel/linux/igb_uio/igb_uio.c:8:
> >  [0m
> >  ./include/linux/atomic-arch-fallback.h:441:2: note: called from 
> > here [0m
> >  441 | arch_atomic_sub(1, v); [0m
> >| ^ [0m
> >  cc1: all warnings being treated as errors [0m
> >  make[6]: *** [scripts/Makefile.build:279: 
> > /home/abuild/rpmbuild/BUILD/dpdk-19.11/arm64-armv8a-linux-gcc/build/kernel/linux/igb_uio/igb_uio.o]
> >  Error 1 [0m
> >  make[5]: *** [Makefile:1805: 
> > /home/abuild/rpmbuild/BUILD/dpdk-19.11/arm64-armv8a-linux-gcc/build/kernel/linux/igb_uio]
> >  Error 2 [0m
> >  make[4]: *** 
> > [/home/abuild/rpmbuild/BUILD/dpdk-19.11/mk/rte.module.mk:51: igb_uio.ko] 
> > Error 2 [0m
> >  make[3]: *** 
> > [/home/abuild/rpmbuild/BUILD/dpdk-19.11/mk/rte.subdir.mk:37: igb_uio] Error 
> > 2 [0m
> >  make[3]: *** Waiting for unfinished jobs [0m
> >  ...
> 
> This is hard to read, please paste raw outputs.
> This error does not ring a bell, this is probably kernel/arch specific.
> I copied Luca who maintains 19.11.
> 
> On the other hand, rather than fixing igb_uio build, why don't you use 
> vfio-pci?

Yeah it's not very readable, unfortunately.

-- 
Kind regards,
Luca Boccassi