From: Thomas Monjalon <thomas@monjalon.net>
To: "Chautru, Nicolas" <nicolas.chautru@intel.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Devlin, Michelle" <michelle.devlin@intel.com>
Subject: Re: Intel roadmap for 22.07
Date: Tue, 29 Mar 2022 20:51:40 +0200 [thread overview]
Message-ID: <2143173.ZfL8zNpBrT@thomas> (raw)
In-Reply-To: <BY5PR11MB44514DC22AE6108164C4FC7EF81E9@BY5PR11MB4451.namprd11.prod.outlook.com>
29/03/2022 17:13, Chautru, Nicolas:
> Hi Thomas,
>
> The ACC101 PMD is to support a new silicon being PRQ this year by Intel. Note this is not a FPGA but an actual ASIC.
> There is some similarity with ACC100 but still a brand new silicon, new features, number of silicon bug fixes, different number of engines, different performance and hence a separate PMD.
> Let me know I unclear
Are you sure you tried hard to manage them with a common code?
Last time we asked such question, it was for DLB,
and it became clear later that it should be the same code,
otherwise you fix bugs two times, etc.
I understand it is a new silicon, but do you know the net driver mlx5
is the same for various hardware of the last 10 years?
> From: Thomas Monjalon <thomas@monjalon.net>
> > 24/03/2022 09:32, Mcnamara, John:
> > > * DLB allow assignment of SW/HW credit quanta assignment on port usage
> > > hint
> > > * DLB allow dlb2 eventdev apps to use specific COS on per port basis
> > > * DLB add support for DLB 2.5 QE weight hardware feature
> >
> > DLB and DLB2 were introduced as different but very similar drivers, and they
> > got eventually merged.
> >
> > > * bbdev new PMD for Intel ACC101 device
> >
> > Is it really going to be a separate driver of ACC100?
next prev parent reply other threads:[~2022-03-29 18:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 8:32 Mcnamara, John
2022-03-29 12:15 ` Thomas Monjalon
2022-03-29 15:13 ` Chautru, Nicolas
2022-03-29 18:51 ` Thomas Monjalon [this message]
2023-07-31 14:12 ` Thomas Monjalon
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=2143173.ZfL8zNpBrT@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=michelle.devlin@intel.com \
--cc=nicolas.chautru@intel.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).