DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: oss-drivers <oss-drivers@corigine.com>
Subject: RE: [PATCH v2 0/3] enhance NFP service framework
Date: Thu, 8 Feb 2024 09:52:03 +0000	[thread overview]
Message-ID: <SJ0PR13MB5545E29010B9CE45AA9BEB6E9E442@SJ0PR13MB5545.namprd13.prod.outlook.com> (raw)
In-Reply-To: <e2311c20-b3ff-45c7-bb62-db9d9ec09871@amd.com>

> On 2/2/2024 3:04 AM, Chaoyong He wrote:
> > Make multiple devices can use single core to run services for flower
> > firmware.
> > Also add synchronize module and service module to support it.
> >
> > ---
> > v2:
> > * Merge the last commit of v1 into the second commit.
> >
> 
> Ask was to move the fix as first patch to make is backportable.
> But by merging last (fix) commit into another one, you are completely loosing the
> capability to backport it to LTS releases.
> 
> I just want to double check if this is intentionally and you don't want to backport
> a fix?
> 

Yes, it's intentionally and we don't want to backport it, thanks.

> 
> > ---
> >
> > Long Wu (3):
> >   net/nfp: add synchronize module
> >   net/nfp: create new service code related files
> >   net/nfp: flower driver uses one service core
> >
> >  drivers/net/nfp/flower/nfp_flower.c           |  56 +--
> >  drivers/net/nfp/flower/nfp_flower_ctrl.c      |  20 +-
> >  drivers/net/nfp/flower/nfp_flower_ctrl.h      |   2 +-
> >  .../net/nfp/flower/nfp_flower_representor.c   |   7 +
> >  drivers/net/nfp/flower/nfp_flower_service.c   | 196 +++++++++
> >  drivers/net/nfp/flower/nfp_flower_service.h   |  17 +
> >  drivers/net/nfp/meson.build                   |   3 +
> >  drivers/net/nfp/nfp_cpp_bridge.c              |  91 +----
> >  drivers/net/nfp/nfp_cpp_bridge.h              |   1 -
> >  drivers/net/nfp/nfp_ethdev.c                  |  31 +-
> >  drivers/net/nfp/nfp_net_common.h              |  15 +-
> >  drivers/net/nfp/nfp_service.c                 | 117 ++++++
> >  drivers/net/nfp/nfp_service.h                 |  20 +
> >  drivers/net/nfp/nfpcore/nfp_sync.c            | 382 ++++++++++++++++++
> >  drivers/net/nfp/nfpcore/nfp_sync.h            |  31 ++
> >  15 files changed, 854 insertions(+), 135 deletions(-)  create mode
> > 100644 drivers/net/nfp/flower/nfp_flower_service.c
> >  create mode 100644 drivers/net/nfp/flower/nfp_flower_service.h
> >  create mode 100644 drivers/net/nfp/nfp_service.c  create mode 100644
> > drivers/net/nfp/nfp_service.h  create mode 100644
> > drivers/net/nfp/nfpcore/nfp_sync.c
> >  create mode 100644 drivers/net/nfp/nfpcore/nfp_sync.h
> >


  reply	other threads:[~2024-02-08  9:52 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-24  9:25 [PATCH 0/4] " Chaoyong He
2024-01-24  9:25 ` [PATCH 1/4] net/nfp: add synchronize module Chaoyong He
2024-01-24  9:25 ` [PATCH 2/4] net/nfp: create new service code related files Chaoyong He
2024-01-24  9:25 ` [PATCH 3/4] net/nfp: flower driver uses one service core Chaoyong He
2024-01-24  9:25 ` [PATCH 4/4] net/nfp: fix stop cpp service problem Chaoyong He
2024-01-30 12:07   ` Ferruh Yigit
2024-01-30 12:17     ` Kevin Traynor
2024-02-02  3:04 ` [PATCH v2 0/3] enhance NFP service framework Chaoyong He
2024-02-02  3:04   ` [PATCH v2 1/3] net/nfp: add synchronize module Chaoyong He
2024-02-02  3:04   ` [PATCH v2 2/3] net/nfp: create new service code related files Chaoyong He
2024-02-02  3:04   ` [PATCH v2 3/3] net/nfp: flower driver uses one service core Chaoyong He
2024-02-06 15:17   ` [PATCH v2 0/3] enhance NFP service framework Ferruh Yigit
2024-02-08  9:52     ` Chaoyong He [this message]
2024-02-08 13:58   ` 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=SJ0PR13MB5545E29010B9CE45AA9BEB6E9E442@SJ0PR13MB5545.namprd13.prod.outlook.com \
    --to=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=oss-drivers@corigine.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).