From: beilei.xing@intel.com
To: qi.z.zhang@intel.com
Cc: dev@dpdk.org, Beilei Xing <beilei.xing@intel.com>
Subject: [PATCH v2 0/5] net/idpf: code refine
Date: Fri, 6 Jan 2023 09:04:56 +0000 [thread overview]
Message-ID: <20230106090501.9106-1-beilei.xing@intel.com> (raw)
In-Reply-To: <20221208072725.32434-1-beilei.xing@intel.com>
From: Beilei Xing <beilei.xing@intel.com>
1. Remove some unnecessary fields from idpf_adapter structure.
2. Fix xmit free for split queue model.
3. Fix driver init symbols.
4. Refine MTU configuration.
V2 changes:
- fix driver init symbols
- refine MTU setting
Jingjing Wu (5):
net/idpf: remove vport req and recv info from adapter
net/idpf: remove req vports from adapter
net/idpf: fix splitq xmit free
net/idpf: fix driver init symbols
net/idpf: refine MTU setting
drivers/net/idpf/idpf_ethdev.c | 301 ++++++++++++++-------------------
drivers/net/idpf/idpf_ethdev.h | 29 ++--
drivers/net/idpf/idpf_rxtx.c | 29 ++--
drivers/net/idpf/idpf_vchnl.c | 18 +-
4 files changed, 166 insertions(+), 211 deletions(-)
--
2.26.2
next prev parent reply other threads:[~2023-01-06 9:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 7:27 [PATCH 0/3] " beilei.xing
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 ` beilei.xing [this message]
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=20230106090501.9106-1-beilei.xing@intel.com \
--to=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--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).