From: Kamaraj P <pkamaraj@gmail.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: dev <dev@dpdk.org>, hpai@cisco.com, "Kamaraj P (kamp)" <kamp@cisco.com>
Subject: Re: DPDK LTS release
Date: Wed, 23 Feb 2022 21:46:34 +0530 [thread overview]
Message-ID: <CAG8PAarL46FqFGxUAswxaNmfCQjqhJEgHP82pSX3w2-EEsm5=Q@mail.gmail.com> (raw)
In-Reply-To: <6728d52d-13e8-2301-3901-8de504531be8@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]
Thanks Kevin.
Apart from release notes to identify changes of DPDK version from 19.11 to
21.11, is there any any major design changes in DPDK ? for example (memory
management, mempool allocation behavior etc)
Please share if there is any pointers.
Thanks,
Kamaraj
On Mon, Feb 21, 2022 at 3:53 PM Kevin Traynor <ktraynor@redhat.com> wrote:
> On 21/02/2022 06:47, Kamaraj P wrote:
> > Hi Team,
> >
>
> Hi,
>
> > We are planning to upgrade the DPDK stable LTS version from DPDK19.11.
> > Could you please suggest what would be the stable LTS version of DPDK ?
> >
>
> If you are looking for an LTS version that will be maintained for the
> longest time in the future, then you can jump to the latest DPDK LTS
> series 21.11.
>
> It will be maintained with backported bugfixes until at least November
> 2023, but we are trialing longer support on some LTS releases so there
> is a possibility it might be extended.
>
> If you take a look at http://core.dpdk.org/roadmap/#stable you can see
> the current roadmap of how long each LTS version is maintained for.
>
> thanks,
> Kevin.
>
> > Thanks,
> > Kamaraj
> >
>
>
[-- Attachment #2: Type: text/html, Size: 1693 bytes --]
next prev parent reply other threads:[~2022-02-23 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 6:47 Kamaraj P
2022-02-21 10:23 ` Kevin Traynor
2022-02-23 16:16 ` Kamaraj P [this message]
2022-02-23 16:57 ` Kevin Traynor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAG8PAarL46FqFGxUAswxaNmfCQjqhJEgHP82pSX3w2-EEsm5=Q@mail.gmail.com' \
--to=pkamaraj@gmail.com \
--cc=dev@dpdk.org \
--cc=hpai@cisco.com \
--cc=kamp@cisco.com \
--cc=ktraynor@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).