Re: release schedule change proposal
On Mon, Nov 15, 2021 at 6:58 AM 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 +1 > > Opinions? > >
Re: [dpdk-users] [Broadcom BNXT] Link event not working
On Wed, Sep 29, 2021 at 3:36 AM Thomas Monjalon wrote: > > 17/09/2021 14:39, Antoine POLLENUS: > > Hi, > > > > I'm experiencing some issues with a Broadcom P225P and DPDK in 19.11.3 > > version. > > > > We register a handler to take care of the link status as specified in the > > DPDK documentation. > > > > But with this specific board the event is never triggered. I tested by > > plugging and unplugging the SFP28 cable. > > > > The issue is kind of problematic because our code relies on this event. > > > > I've tested with an intel xxv710-da2 and with that board no problem. > > > > Is it normal that this link status event is not working on Broadcom ? > > > > Is it fixed in an higher version ? > > Possible, please try testpmd with a recent DPDK. > If it doesn't work on DPDK 21.08, then you can open a bug in bugs.dpdk.org. Yes, please try with the latest. And if it does not work, you can report the bug. Please provide firmware version on the card. Thanks Ajit > > Thanks > >
Re: [dpdk-users] [DISCUSSION] code snippet documentation
On Thu, Jul 22, 2021 at 1:29 PM Thomas Monjalon wrote:
>
> 15/07/2021 09:01, Asaf Penso:
> > Hello DPDK community,
> >
> > I would like to bring up a discussion about a way to have code snippets as
> > an example for proper usage.
> > The DPDK tree is filled with great pieces of code that are well documented
> > and maintained in high quality.
> > I feel we are a bit behind when we talk about usage examples.
> >
> > One way, whenever we implement a new feature, is to extend one of the
> > test-* under the "app" folder.
> > This, however, provides means to test but doesn't provide a good usage
> > example.
> >
> > Another way is to check the content of the "example" folder and whenever we
> > have a BIG new feature it seems like a good place.
> > This, however, doesn't provide a good option when we talk about small
> > features.
> > If, for example, we extend rte_flow with an extra action then providing a
> > full-blown example application is somewhat an entry barrier.
> >
> > A third option could be to document it in one of the .rst files we have.
> > Obviously, this requires high maintenance and no option to assure it still
> > compiles.
> >
> > I'd like to propose another approach that will address the main two issues:
> > remove the entry barrier and assure compilation.
> > In this approach, inside the "examples" folder we'll create another folder
> > for "snippets".
> > Inside "snippets" we'll have several files per category, for example,
> > rte_flow_snippets.c
> > Each .c file will include a main function that calls the different use
> > cases we want to give as an example.
> > The purpose is not to generate traffic nor read rx/tx packets from the DPDK
> > ports.
> > The purpose is to have a good example that compiles properly.
> >
> > Taking the rte_flow_snippets.c as an example its main function would look
> > like this:
> >
> > int
> > main(int argc, char **argv)
> > {
> > rte_flow_snippet_match_5tuple_and_drop();
> > rte_flow_snippet_match_geneve_ope_and_rss();
> > ...
> > Return 0;
> > }
>
> I think we need to have a policy or justification about which snippet
> is worth to have.
> My thought is to avoid creating snippets which have no other value
> than showing a function call.
> I think there is a value if the context is not simple.
I agree. Otherwise it will be cluttered with snippets.
>
>
> Please could you provide a more complex example?
>
>
Re: [dpdk-users] How to contribute to DPDK
On Mon, Feb 10, 2020 at 9:51 AM Kevin Traynor wrote: > On 03/02/2020 07:35, Waqqas Jabbar wrote: > > Hi > > > > Hi, > > > I would like to contribute to DPDK project. Please share where should I > begin. > > Cool :-) > > > I was thinking of starting with some bugs at > > https://bugs.dpdk.org/describecomponents.cgi?product=DPDK > > > > What's the process to do that? Who assigns the bug or can I opt for one? > > Can anyone suggest some easy bugs to fix? > > > > I think Ajit assigns the bugs, but I suggest that if there's something > you are interested in fixing, don't wait, just go for it. > Yes. This could be easier than I assigning any bug to you > > Depending on experience, some bugs may be complex, so something like > docs, testing or some small cleanup patches can be a good place to start. > > As a new user, maybe you think some things are badly explained (or not > at all) and could use additional documentation? There are unit tests for > many components, maybe you see some missing cases? or maybe some parts > of the code are not clear and need to be cleaned up. > Yes, I agree. These are all good areas to start with. Thanks Ajit > > Note, there's a section about how to contribute code to DPDK here > http://doc.dpdk.org/guides/contributing/patches.html > > Kevin. > > > Regards > > Waqqas > > > >
