DPDK patches and discussions
 help / color / mirror / Atom feed
From: beilei.xing@intel.com
To: jingjing.wu@intel.com, qi.z.zhang@intel.com
Cc: dev@dpdk.org, Beilei Xing <beilei.xing@intel.com>
Subject: [PATCH 0/3] net/idpf: code refine
Date: Thu,  8 Dec 2022 07:27:22 +0000	[thread overview]
Message-ID: <20221208072725.32434-1-beilei.xing@intel.com> (raw)

From: Beilei Xing <beilei.xing@intel.com>

1. Remove some unnecessary fields from idpf_adapter structure.
2. Fix xmit free for split queue model.

Jingjing Wu (3):
  net/idpf: remove vport req and recv info from adapter
  net/idpf: remove req vports from adapter
  net/idpf: fix splitq xmit free

 drivers/net/idpf/idpf_ethdev.c | 258 +++++++++++++--------------------
 drivers/net/idpf/idpf_ethdev.h |  28 ++--
 drivers/net/idpf/idpf_rxtx.c   |  29 ++--
 drivers/net/idpf/idpf_vchnl.c  |  18 +--
 4 files changed, 139 insertions(+), 194 deletions(-)

-- 
2.26.2


             reply	other threads:[~2022-12-08  7:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-08  7:27 beilei.xing [this message]
2022-12-08  7:27 ` [PATCH 1/3] net/idpf: remove vport req and recv info from adapter beilei.xing
2022-12-08  7:27 ` [PATCH 2/3] net/idpf: remove req vports " beilei.xing
2022-12-08  7:27 ` [PATCH 3/3] net/idpf: fix splitq xmit free beilei.xing
2023-01-06  9:04 ` [PATCH v2 0/5] net/idpf: code refine beilei.xing
2023-01-06  9:04   ` [PATCH v2 1/5] net/idpf: remove vport req and recv info from adapter beilei.xing
2023-01-06  9:04   ` [PATCH v2 2/5] net/idpf: remove req vports " beilei.xing
2023-01-06  9:04   ` [PATCH v2 3/5] net/idpf: fix splitq xmit free beilei.xing
2023-01-06  9:05   ` [PATCH v2 4/5] net/idpf: fix driver init symbols beilei.xing
2023-01-06  9:05   ` [PATCH v2 5/5] net/idpf: refine MTU setting beilei.xing
2023-01-16  7:59   ` [PATCH v2 0/5] net/idpf: code refine Zhang, Qi Z

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=20221208072725.32434-1-beilei.xing@intel.com \
    --to=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=qi.z.zhang@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).