DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Leyi Rong <leyi.rong@intel.com>, Qi Zhang <qi.z.zhang@intel.com>,
	 Bruce Richardson <bruce.richardson@intel.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	 Ali Alnubani <alialnu@nvidia.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/ice: add AVX512BW flag check both in build and runtime
Date: Tue, 27 Oct 2020 14:17:25 +0100	[thread overview]
Message-ID: <CAJFAV8z8BBvqV=ka=-P=AyiHfOgnftYP6kqct2jRe+ZMvE9=AA@mail.gmail.com> (raw)
In-Reply-To: <f51962fe-5a0a-4c4e-cd7d-32dc76403acd@intel.com>

On Tue, Oct 27, 2020 at 12:57 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:
>
> On 10/27/2020 10:19 AM, Leyi Rong wrote:
> > Intrinsic function __mm512_bsrli_epi128 should be used in
> > the environment which supports AVX512BW, so adds check for
> > this flag.
> >
> > Fixes: 5dd3b8f3af34 ("net/ice: add AVX512 vector path")
> >
> > Signed-off-by: Leyi Rong <leyi.rong@intel.com>
>
> Squashed into relevant commit in next-net, thanks.
>
>
> Andrew, Ali, David,
>
> Can you please confirm the issue is solved in the next-net/main?

Tree with HEAD at 5e12432f4be4 ("net/ice: fix Rx offload flags in SSE
path") looks good to me.
Thanks.

-- 
David Marchand


  parent reply	other threads:[~2020-10-27 13:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 10:19 Leyi Rong
2020-10-27 11:57 ` Ferruh Yigit
2020-10-27 12:47   ` Andrew Rybchenko
2020-10-27 13:12   ` Ali Alnubani
2020-10-27 13:27     ` Bruce Richardson
2020-10-27 15:36       ` Rong, Leyi
2020-10-27 15:57         ` Bruce Richardson
2020-10-27 13:17   ` David Marchand [this message]
2020-11-02  8:22     ` Ali Alnubani

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='CAJFAV8z8BBvqV=ka=-P=AyiHfOgnftYP6kqct2jRe+ZMvE9=AA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=alialnu@nvidia.com \
    --cc=arybchenko@solarflare.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=leyi.rong@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=wenzhuo.lu@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).