From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg0-f54.google.com (mail-pg0-f54.google.com [74.125.83.54]) by dpdk.org (Postfix) with ESMTP id 918795B40 for ; Fri, 23 Feb 2018 20:38:07 +0100 (CET) Received: by mail-pg0-f54.google.com with SMTP id y26so3732894pgv.4 for ; Fri, 23 Feb 2018 11:38:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=9/WSGwVI5TT7cxmH3zYh56+mC2Jzj7y3R77a6ZCV9qk=; b=U4FVpU1MmahvJ3dC2aSiG9k5RT11aUTiOlrOhXF6toWhoruVZnTCsEhjv96J0I54Sf EfnBsDp5auDAIsCewLAEv2joiiGZSK3OS8XZVnOE+scJTFam37VM8LOKT4V771ScLF69 NZHX4wCUCxJnG4ERzc8IH8Q6Y79r1cXl8EaXl9VuBLbbcifedVYapbVaZbikG1CoNnDN h8BqoS3Qw4sao9Njw/Fl3aYrAa9ItChEcOR+opTpTTmgZULyo5++wGTxy+lT47yJ9mUu 5fRfHbh7O507jg0BtYHD+4LZtmg1PyDK4kejsZOGrviz45TGn7qOvIZ7WJbD6LQUXD3k Kdig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=9/WSGwVI5TT7cxmH3zYh56+mC2Jzj7y3R77a6ZCV9qk=; b=UuUPoNNKj3x5o3fadaWiHt9ZvYZklqz4YpQ97n77vnJcA8hDr+ylUOLrI7pOJG3dA5 vuxlPkBFSRFdSwQVUODQ/wsubTDXyecQwDirCVwUjEcLoJXaFaAB1llvMLoxLqyVYwMU u8BdbeJIUzKsVs0hMUv2c58bi2bAGcwMHcI0ufSJQAZDR+AEtpexV8MhkSkVbRahIDn6 3qM1O+W3hvE9cm/E3TBIQbR9h/I11bJkT4EKpQKTBhriUu4+0ObJ5u9TVaDQ4ARypvwN BVsd01bP9aA3uI1cmqLNUJaC74W1Ff9drC0OspQ04NTDzL12D7m1ch3GKkUAP2x6nrti 9NXQ== X-Gm-Message-State: APf1xPDe69Y5DWE6XZMQvPZWgTE4ykOs7wFgR1mGIqCQClqYMYPUlZ+T z30O6L0sn+5yH54qULUwZT3XHg== X-Google-Smtp-Source: AH8x226v9ftN6B+aVAZ8dMaNwZ8P+nDVBcMZ1Oo2tnoKu0nHBCrPmOBWXxEp8XtIvtmGNJJjcdFGqg== X-Received: by 10.98.15.137 with SMTP id 9mr2782829pfp.216.1519414686633; Fri, 23 Feb 2018 11:38:06 -0800 (PST) Received: from xeon-e3 (204-195-71-95.wavecable.com. [204.195.71.95]) by smtp.gmail.com with ESMTPSA id r14sm6098349pfa.136.2018.02.23.11.38.06 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 23 Feb 2018 11:38:06 -0800 (PST) Date: Fri, 23 Feb 2018 11:38:04 -0800 From: Stephen Hemminger To: Tharaneedharan Vilwanathan Cc: users@dpdk.org Message-ID: <20180223113804.7894413f@xeon-e3> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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: Fri, 23 Feb 2018 19:38:08 -0000 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.