From: Harman Kalra <hkalra@marvell.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Kiran Kumar K <kirankumark@marvell.com>, <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v2] net/octeontx2: add cn98xx support
Date: Fri, 26 Jun 2020 19:04:03 +0530 [thread overview]
Message-ID: <20200626133401.GA102895@outlook.office365.com> (raw)
In-Reply-To: <a477d278-dc42-5082-d242-7aab25d042f3@intel.com>
On Fri, Jun 26, 2020 at 10:40:16AM +0100, Ferruh Yigit wrote:
> External Email
>
> ----------------------------------------------------------------------
> On 6/24/2020 1:46 PM, Harman Kalra wrote:
> > New cn98xx SOC comes up with two NIX blocks wrt
> > cn96xx, cn93xx, to achieve higher performance.
> > Also the no of cores increased to 36 from 24.
> >
> > Adding support for cn98xx where need a logic to
> > detect if the LF is attached to NIX0 or NIX1 and
> > then accordingly use the respective NIX block.
> >
> > Signed-off-by: Harman Kalra <hkalra@marvell.com>
> > ---
> > *V2: updated make/meson configs with the increased no of
> > cores.
>
> Since this is new SoC support I think can be good to highlight in the release
> notes, what do you think?
Yes, this PMD update information should be captured in release notes.
But since this patch has already been merged to dpdk-next-net-mrvl tree,
so can I send a new patch with release notes only and later you can
squash both the patches together.
Thanks
Harman
next prev parent reply other threads:[~2020-06-26 13:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 15:05 [dpdk-dev] [PATCH] " Harman Kalra
2020-06-24 8:59 ` Jerin Jacob
2020-06-24 12:46 ` [dpdk-dev] [PATCH v2] " Harman Kalra
2020-06-25 15:33 ` Jerin Jacob
2020-06-26 9:40 ` Ferruh Yigit
2020-06-26 13:34 ` Harman Kalra [this message]
2020-06-26 13:45 ` [dpdk-dev] [EXT] " Ferruh Yigit
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=20200626133401.GA102895@outlook.office365.com \
--to=hkalra@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=kirankumark@marvell.com \
--cc=marko.kovacevic@intel.com \
--cc=ndabilpuram@marvell.com \
--cc=thomas@monjalon.net \
/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).