DPDK usage discussions
 help / color / mirror / Atom feed
From: "Lombardo, Ed" <Ed.Lombardo@netscout.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
	Cliff Burdick <shaklee3@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: RE: How to increase mbuf size in dpdk version 17.11
Date: Wed, 2 Mar 2022 05:48:08 +0000	[thread overview]
Message-ID: <SJ0PR01MB6399DB6F5626C6C318C330568F039@SJ0PR01MB6399.prod.exchangelabs.com> (raw)
In-Reply-To: <20220301204038.7da0aa7b@hermes.local>

I am using vmware hypervisor.

-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org> 
Sent: Tuesday, March 1, 2022 11:41 PM
To: Cliff Burdick <shaklee3@gmail.com>
Cc: Lombardo, Ed <Ed.Lombardo@netscout.com>; users@dpdk.org
Subject: Re: How to increase mbuf size in dpdk version 17.11

External Email: This message originated outside of NETSCOUT. Do not click links or open attachments unless you recognize the sender and know the content is safe.

On Tue, 1 Mar 2022 19:56:39 -0800
Cliff Burdick <shaklee3@gmail.com> wrote:

> That's showing you have 0 hugepages free. Maybe they weren't passed 
> through to the VM properly?

Which hypervisor? Not all hypervisors really support hugepages.

  reply	other threads:[~2022-03-02  5:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 18:34 Lombardo, Ed
2022-03-01 19:56 ` Stephen Hemminger
2022-03-01 21:30   ` Lombardo, Ed
2022-03-01 21:37     ` Cliff Burdick
2022-03-01 22:46       ` Stephen Hemminger
2022-03-02  1:37         ` Lombardo, Ed
2022-03-02  3:45           ` Cliff Burdick
2022-03-02  3:50             ` Lombardo, Ed
2022-03-02  3:56               ` Cliff Burdick
2022-03-02  4:40                 ` Stephen Hemminger
2022-03-02  5:48                   ` Lombardo, Ed [this message]
2022-03-02 14:47                     ` Cliff Burdick
2022-03-02 14:20                 ` Lombardo, Ed

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=SJ0PR01MB6399DB6F5626C6C318C330568F039@SJ0PR01MB6399.prod.exchangelabs.com \
    --to=ed.lombardo@netscout.com \
    --cc=shaklee3@gmail.com \
    --cc=stephen@networkplumber.org \
    --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).