All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sun, QinX" <qinx.sun@intel.com>
To: "Zhang, AlvinX" <alvinx.zhang@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"Rong, Leyi" <leyi.rong@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Zhang, AlvinX" <alvinx.zhang@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v3] net/ice: fix secondary process Rx offload path
Date: Tue, 16 Nov 2021 03:09:07 +0000	[thread overview]
Message-ID: <SJ0PR11MB48639B86E6D3E05C00E29A1E87999@SJ0PR11MB4863.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20211116023209.18252-1-alvinx.zhang@intel.com>

> -----Original Message-----
> From: Alvin Zhang <alvinx.zhang@intel.com>
> Sent: Tuesday, November 16, 2021 10:32 AM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Rong, Leyi <leyi.rong@intel.com>
> Cc: dev@dpdk.org; Zhang, AlvinX <alvinx.zhang@intel.com>;
> stable@dpdk.org
> Subject: [PATCH v3] net/ice: fix secondary process Rx offload path
> 
> Secondary process depends on the vector offload flag to select right Rx
> offload path. This patch adds a variable in share memory to store the vector
> offload flag that can be directly read by secondary process.
> 
> Fixes: 808a17b3c1e6 ("net/ice: add Rx AVX512 offload path")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Alvin Zhang <alvinx.zhang@intel.com>

Tested-by: Qin Sun <qinx.sun@intel.com>



  reply	other threads:[~2021-11-16  3:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-12  5:43 [PATCH] net/ice: fix secondary process Rx offload path Alvin Zhang
2021-11-15  2:05 ` [PATCH v2] " Alvin Zhang
2021-11-16  1:21   ` Zhang, Qi Z
2021-11-16  2:12     ` Zhang, AlvinX
2021-11-16  2:32   ` [PATCH v3] " Alvin Zhang
2021-11-16  3:09     ` Sun, QinX [this message]
2021-11-16  4:54       ` 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=SJ0PR11MB48639B86E6D3E05C00E29A1E87999@SJ0PR11MB4863.namprd11.prod.outlook.com \
    --to=qinx.sun@intel.com \
    --cc=alvinx.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=leyi.rong@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=stable@dpdk.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.