DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Nitin Katiyar <nitin.katiyar@aryaka.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Failed to enable SRIOV
Date: Thu, 25 Jan 2024 15:55:52 -0800	[thread overview]
Message-ID: <20240125155552.2e19e52d@hermes.local> (raw)
In-Reply-To: <PSAPR01MB3781F58097E36E93C468AE5F937A2@PSAPR01MB3781.apcprd01.prod.exchangelabs.com>

On Thu, 25 Jan 2024 09:13:55 +0000
Nitin Katiyar <nitin.katiyar@aryaka.com> wrote:

> Hi,
> I am trying to enable SR-IOV on linux server (details below) and it throws following error:
> # echo '4' > /sys/class/net/enp1s0f0/device/sriov_numvfs
> -bash: echo: write error: Cannot allocate memory
> 
> I went through some of articles on internet and it suggested some grub changes for pci but none of them helped. Following are the details of system and error
> 
> System details:
> -------------------
> Rocky Linux release 9.3 (Blue Onyx)
> 
> model name      : Intel(R) Xeon(R) E-2236 CPU @ 3.40GHz
> flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp vnmi md_clear flush_l1d arch_capabilities
> vmx flags       : vnmi preemption_timer invvpid ept_x_only ept_ad ept_1gb flexpriority tsc_offset vtpr mtf vapic ept vpid unrestricted_guest ple shadow_vmcs pml ept_mode_based_exec
> 
> 
> ixgbe ver:       5.14.0-362.8.1.el9_3.x86_64 
> 


You may be running into an issue with the limit on the number of interrupt vectors the device supports (hardware limit).
What is the total number of MSI-X vectors across the total number of VF's?

  reply	other threads:[~2024-01-25 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-25  9:13 Nitin Katiyar
2024-01-25 23:55 ` Stephen Hemminger [this message]
2024-02-04  6:43 ` Nitin Katiyar
2024-02-05  3:22   ` Yang, Tao Y

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=20240125155552.2e19e52d@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=nitin.katiyar@aryaka.com \
    --cc=users@dpdk.org \
    /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).