From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com [209.85.218.51]) by dpdk.org (Postfix) with ESMTP id 8EF625F4D for ; Wed, 14 Mar 2018 06:34:50 +0100 (CET) Received: by mail-oi0-f51.google.com with SMTP id j79so1709064oib.12 for ; Tue, 13 Mar 2018 22:34:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AYF9BxKERjKbchKlfJalumEYQw34G7m+CZiMGWGHpik=; b=OZI6w6krwIcLba1/agP/JfmmTOzJKUpgtZRQIYH7VQ/pbaEkG1Qc2dOyIlasx7b86x vIpcnx6RvHHebW/h0Ej+H7GaGYu3OOByu6Z/1pDRFbKSv4MinWWMoXkOdWrBgkrrCV5i doFCMkkNKeKczP6dyqqmA+VBWwHehTtUq5v6oJCnJq8kV61sLVaa6+d4BUDYMSezOsRC EGP5/lUtsRjpcv9o8CeUTphlQvFHSZYBTigTl63owx68Eid1dujg9k0AbzMcaEgcrc3y fBIMTsAi4Jqf9HJsmrPtgHGHeXBjcyAACCRDjIuJL3cwnuSDCWDHbSGm62OYAheuKLVE EJRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AYF9BxKERjKbchKlfJalumEYQw34G7m+CZiMGWGHpik=; b=tow5t0ymj6j6IFvZfyfimgD/KHtXX4Qm6QRAt8Yd7EqqemB95WSnJRJqo/Xv9IeCgq 4CjWho+UU24Ofiw60gVlHBE2K2dYWP6NkA46jxFbmlhO8QVNP1aWBhlf2wMpGVZXXfX+ qBzlmavTrIepggKFY0+hs/iK0iktWJ7UcSld+6zugqhTHyouOt/cLCY5nOW8Tja0QUqB v8qDS13GaxsgFhN0139HNiNvrg8M/wFV9wE+4wOLdkcUyLdVuTFGVDVdvW9ZhzqXpOxN l9ietzzJMx2hxim6+PlDk6yb290crhNaTyd04rSFncqpEFjCCK36wRYYNk06iyPKCUkQ wRbw== X-Gm-Message-State: AElRT7FaCMROEzOkRnmsKti1VBjOaiv7IzJ2VHqkNfgXOVYQK4HzunNL L+Wa5CaD+Qt28ENXxDyrbnhj1XSoFPpOVHP/1U8= X-Google-Smtp-Source: AG47ELtOG9L+WgqbKdVASC9vBE/lZHjE9JuCzcYknp3pkb+YyA3ihnWxMk4chPBh5MvXAXTbMAgBrHm/g1dUbmKBIn8= X-Received: by 10.202.62.135 with SMTP id l129mr1909488oia.333.1521005689805; Tue, 13 Mar 2018 22:34:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.74.4.205 with HTTP; Tue, 13 Mar 2018 22:34:49 -0700 (PDT) In-Reply-To: References: <20180223113804.7894413f@xeon-e3> From: Tharaneedharan Vilwanathan Date: Tue, 13 Mar 2018 22:34:49 -0700 Message-ID: To: Don maillist Cc: Stephen Hemminger , users Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] AVX-512 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2018 05:34:50 -0000 Hi Don, Thanks for sharing your thoughts. The CPU I have is: "Intel(R) Xeon(R) Gold 6130 CPU @ 2.10GHz" Would what you say apply to this as well? Anyway, the prime reason why I am having this server is to play with AVX-512. So I would like to try it. Regards dharani On Tue, Mar 13, 2018 at 8:20 PM, Don maillist wrote: > 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 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. >> > >> > >