DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Marchand <david.marchand@redhat.com>, dev <dev@dpdk.org>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>,
	Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
	"Dmitry Malloy (MESHCHANINOV)" <dmitrym@microsoft.com>,
	Pallavi Kadam <pallavi.kadam@intel.com>,
	Beilei Xing <beilei.xing@intel.com>, Jeff Guo <jia.guo@intel.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>,
	Leyi Rong <leyi.rong@intel.com>,
	Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: disable AVX512 for Windows
Date: Wed, 20 Jan 2021 17:56:16 +0000	[thread overview]
Message-ID: <67d98082-0ff1-8751-8d12-f18b7ce72208@intel.com> (raw)
In-Reply-To: <CAJFAV8wj2=iFfMa7z3HnUR7A5z1Y2M2SZaQQJZ+gWZgDaL3K4Q@mail.gmail.com>

On 1/20/2021 5:46 PM, David Marchand wrote:
> On Wed, Jan 20, 2021 at 5:40 PM David Marchand
> <david.marchand@redhat.com> wrote:
>> There is probably better to do rather than disabling AVX512 globally for
>> Windows but since I saw no patch fixing this, here it is.
> 
> Interesting...
> This patch does not work with UNH job.
> Seeing the same error but now on a different file, I am not sure what is wrong.
> 
> 

I have just replied to the original thread [1], the problem seems not just 
related to the 'i40e_rxtx_vec_avx512.c'.

[1]
http://inbox.dpdk.org/dev/20201215021945.103396-1-leyi.rong@intel.com/T/#mc47abfa0b72b068f26f4b8deb0dacea840d721e9

  reply	other threads:[~2021-01-20 17:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 16:40 David Marchand
2021-01-20 17:46 ` David Marchand
2021-01-20 17:56   ` Ferruh Yigit [this message]
2021-01-20 18:21 ` Dmitry Kozlyuk
2021-01-20 18:24   ` Ferruh Yigit
2021-01-20 19:27     ` Dmitry Kozlyuk

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=67d98082-0ff1-8751-8d12-f18b7ce72208@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=dmitrym@microsoft.com \
    --cc=jia.guo@intel.com \
    --cc=leyi.rong@intel.com \
    --cc=navasile@linux.microsoft.com \
    --cc=pallavi.kadam@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).