DPDK usage discussions
 help / color / mirror / Atom feed
From: Don maillist <dlw.mailist@gmail.com>
To: Tharaneedharan Vilwanathan <vdharani@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>, users <users@dpdk.org>
Subject: Re: [dpdk-users] AVX-512
Date: Tue, 13 Mar 2018 22:20:13 -0500	[thread overview]
Message-ID: <CABCaf40bD5FzQfcwypb6rvjZFcin3vKprsLs-9YMAMSqZx+51g@mail.gmail.com> (raw)
In-Reply-To: <CAN-HoCkxUTcn19iLpmcz08FuttPem4daLLHLpn4xv+4aP_t94w@mail.gmail.com>

Be careful with AVX-512. It is best to use AVX-256 on Skylake. The AVX-512
applications do not run efficiently today on Skylake. It increases power
consumption in the underlying cores.

Best Regards,
Don

On Thu, Mar 1, 2018 at 7:57 PM, Tharaneedharan Vilwanathan <
vdharani@gmail.com> wrote:

> Hi Stephen,
>
> Appreciate your response.
>
> I have ESXi. I am still trying to map the KVM config with ESXi but no luck
> yet. I have requested the admin to figure out. If anyone is familiar with
> ESXi configuration for this, please let me know.
>
> Thanks
> dharani
>
> On Fri, Feb 23, 2018 at 11:38 AM, Stephen Hemminger <
> stephen@networkplumber.org> wrote:
>
> > On Fri, 23 Feb 2018 11:16:14 -0800
> > Tharaneedharan Vilwanathan <vdharani@gmail.com> wrote:
> >
> > > Hi All,
> > >
> > > I have a quick question. I got a new server with the CPU that should
> have
> > > AVX-512 support but I don't see it in Linux (Ubuntu 18.04).
> > >
> > > Here is the output:
> > >
> > > auto@auto-virtual-machine:~$ *cat /proc/cpuinfo*
> > > processor : 0
> > > vendor_id : GenuineIntel
> > > cpu family : 6
> > > model : 85
> > > model name : *Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz*
> > > stepping : 4
> > > microcode : 0x2000029
> > > cpu MHz : 2095.078
> > > cache size : 22528 KB
> > > physical id : 0
> > > siblings : 2
> > > core id : 0
> > > cpu cores : 2
> > > apicid : 0
> > > initial apicid : 0
> > > fpu : yes
> > > fpu_exception : yes
> > > cpuid level : 22
> > > wp : yes
> > > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat
> > > pse36 clflush dts mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm
> > > constant_tsc arch_perfmon pebs bts nopl xtopology tsc_reliable
> > nonstop_tsc
> > > cpuid pni pclmulqdq ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe
> popcnt
> > > tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm
> > > 3dnowprefetch cpuid_fault invpcid_single pti fsgsbase tsc_adjust bmi1
> hle
> > > avx2 smep bmi2 invpcid rtm rdseed adx smap xsaveopt arat
> > > bugs : cpu_meltdown spectre_v1 spectre_v2
> > > bogomips : 4190.15
> > > clflush size : 64
> > > cache_alignment : 64
> > > address sizes : 42 bits physical, 48 bits virtual
> > > power management:
> > >
> > > Can someone tell me why I don't see AVX-512?
> > >
> > > Appreciate your help.
> > >
> > > Thanks
> > > dharani
> >
> > If you are running in a VM, make sure that your hypervisor passes the avx
> > flags through.
> > In KVM this is usually done with the "Copy host CPU configuration" in
> virt
> > manager.
> >
>

  reply	other threads:[~2018-03-14  3:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-23 19:16 Tharaneedharan Vilwanathan
2018-02-23 19:38 ` Stephen Hemminger
2018-03-02  1:57   ` Tharaneedharan Vilwanathan
2018-03-14  3:20     ` Don maillist [this message]
2018-03-14  5:34       ` Tharaneedharan Vilwanathan

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=CABCaf40bD5FzQfcwypb6rvjZFcin3vKprsLs-9YMAMSqZx+51g@mail.gmail.com \
    --to=dlw.mailist@gmail.com \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    --cc=vdharani@gmail.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).