DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xing, Beilei" <beilei.xing@intel.com>
To: "Liu, Mingxia" <mingxia.liu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Wu, Jingjing" <jingjing.wu@intel.com>
Subject: RE: [PATCH v2] net/idpf: refine Rx/Tx queue model info
Date: Thu, 2 Mar 2023 12:08:46 +0000	[thread overview]
Message-ID: <LV2PR11MB59974521EFAEA083BC43F9ECF7B29@LV2PR11MB5997.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230301192659.601892-1-mingxia.liu@intel.com>



> -----Original Message-----
> From: Liu, Mingxia <mingxia.liu@intel.com>
> Sent: Thursday, March 2, 2023 3:27 AM
> To: dev@dpdk.org
> Cc: Wu, Jingjing <jingjing.wu@intel.com>; Xing, Beilei <beilei.xing@intel.com>;
> Liu, Mingxia <mingxia.liu@intel.com>
> Subject: [PATCH v2] net/idpf: refine Rx/Tx queue model info
> 
> This patch updates queue mode info in struct idpf_adapter.
> Using is_rx_singleq_model to diffentiate rx_singq and rx_splitq explicitly,
> instead of deducing it from pointer values.
> 
> Signed-off-by: Mingxia Liu <mingxia.liu@intel.com>

Acked-by: Beilei Xing <beilei.xing@intel.com>

  parent reply	other threads:[~2023-03-02 12:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 16:16 [PATCH] net/idpf: optimize Tx/Rx qeue mode code Mingxia Liu
2023-03-01 19:26 ` [PATCH v2] net/idpf: refine Rx/Tx queue model info Mingxia Liu
2023-03-02  9:46   ` Zhang, Qi Z
2023-03-02 10:06     ` Ferruh Yigit
2023-03-02 10:28       ` Zhang, Qi Z
2023-03-02 11:38         ` Liu, Mingxia
2023-03-02 12:08   ` Xing, Beilei [this message]
2023-03-02 19:51   ` [PATCH v3] " Mingxia Liu
2023-03-02 14:42     ` 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=LV2PR11MB59974521EFAEA083BC43F9ECF7B29@LV2PR11MB5997.namprd11.prod.outlook.com \
    --to=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=mingxia.liu@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).