From: "Yan, Zhirun" <zhirun.yan@intel.com>
To: Jerin Jacob <jerinjacobk@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"kirankumark@marvell.com" <kirankumark@marvell.com>,
"ndabilpuram@marvell.com" <ndabilpuram@marvell.com>,
"Fu, Qi" <qi.fu@intel.com>
Subject: RE: [PATCH v2] graph: fix graph model check in core binding
Date: Wed, 5 Jul 2023 00:50:41 +0000 [thread overview]
Message-ID: <SN7PR11MB67750C49E943C2A5F7891D54852FA@SN7PR11MB6775.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1MgohJfB-dcbdYA=AFVd59Qzsg3hh2==U92MhEReYLgCQ@mail.gmail.com>
> -----Original Message-----
> From: Jerin Jacob <jerinjacobk@gmail.com>
> Sent: Tuesday, July 4, 2023 5:10 PM
> To: Yan, Zhirun <zhirun.yan@intel.com>
> Cc: dev@dpdk.org; jerinj@marvell.com; kirankumark@marvell.com;
> ndabilpuram@marvell.com; Fu, Qi <qi.fu@intel.com>
> Subject: Re: [PATCH v2] graph: fix graph model check in core binding
>
> On Mon, Jul 3, 2023 at 3:35 PM Zhirun Yan <zhirun.yan@intel.com> wrote:
> >
> > Fix graph model check in core binding with graph. And
> > rte_graph_clone() need to use valid params rather than NULL pointer.
> > Update release notes for new mcore dispatch model.
>
>
> Please add Fixes:
Ok.
>
> > Signed-off-by: Zhirun Yan <zhirun.yan@intel.com>
> > ---
> > app/test/test_graph.c | 15 ++++++++++++---
> > doc/guides/rel_notes/release_23_07.rst | 12 ++++++++++++
> > lib/graph/graph.c | 2 +-
> > 3 files changed, 25 insertions(+), 4 deletions(-)
>
> > +* **Added mcore dispatch model in rte_graph library.**
> > +
> > + * Added set, get and validate model APIs to enhance graph framework
> > + to chose different walk models.
>
> Adding one line for what is "mcore dispatch model" will be good.
>
Got it. Will add in next version.
> > + * Added clone graph, bind graph with lcore and affinity node with
> > + lcore APIs to support mcore dispatch model.
>
> I think, Above, statement, you can remove.
Yes. Thanks.
>
> > +
> > * **Added PDCP Library.**
> >
> > Added an experimental library to provide PDCP UL and DL processing of
> packets.
> > @@ -200,6 +207,11 @@ New Features
> >
> > Enhanced the GRO library to support TCP packets over IPv6 network.
> >
> > +* **Update l3fwd-graph sample application.**
> > +
> > + Added a new cmdline option ``--model`` which can be used to chose
> > + RTC or mcore dispatch model.
> > +
next prev parent reply other threads:[~2023-07-05 0:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:29 [PATCH v1] " Zhirun Yan
2023-07-03 9:55 ` [PATCH v2] " Zhirun Yan
2023-07-04 9:10 ` Jerin Jacob
2023-07-05 0:50 ` Yan, Zhirun [this message]
2023-07-05 1:56 ` [PATCH v3] " Zhirun Yan
2023-07-07 10:16 ` Jerin Jacob
2023-07-10 5:08 ` Yan, Zhirun
2023-07-10 7:15 ` [PATCH v4 0/2] fix graph issues Zhirun Yan
2023-07-10 7:15 ` [PATCH v4 1/2] graph: fix graph functional tests with valid params Zhirun Yan
2023-07-10 9:21 ` Jerin Jacob
2023-07-10 7:15 ` [PATCH v4 2/2] graph: fix graph model check in core binding Zhirun Yan
2023-07-10 9:29 ` Jerin Jacob
2023-07-12 14:01 ` [PATCH v4 0/2] fix graph issues 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=SN7PR11MB67750C49E943C2A5F7891D54852FA@SN7PR11MB6775.namprd11.prod.outlook.com \
--to=zhirun.yan@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=qi.fu@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).