DPDK patches and discussions
 help / color / mirror / Atom feed
From: Saurabh Mishra <saurabh.globe@gmail.com>
To: users@dpdk.org, dev@dpdk.org
Subject: [dpdk-dev] Huge pages to be allocated based on number of mbufs
Date: Mon, 14 Mar 2016 10:54:58 -0700	[thread overview]
Message-ID: <CAMnwyJ11qXeRA1=6P4rxivZMOEcoV+K0hOCvXe2W04PkksHS1g@mail.gmail.com> (raw)

Hi,

We are planning to support virtio, vmxnet3, ixgbe, i40e, bxn2x and SR-IOV
on some of them with DPDK.

We have seen that even if we give correct number of mbufs given the number
hugepages reserved, rte_eth_tx_queue_setup() may still fail with no enough
memory (I saw this on i40evf but worked on virtio and vmxnet3).

We like to know what's the recommended way to determine how many hugepages
we should allocate given the number of mbufs such that queue setup APIs
also don't fail.

Since we will be running on low-end systems too we need to be careful about
reserving hugepages.

Thanks,
/Saurabh

             reply	other threads:[~2016-03-14 17:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 17:54 Saurabh Mishra [this message]
2016-03-17 17:25 ` Zoltan Kiss

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='CAMnwyJ11qXeRA1=6P4rxivZMOEcoV+K0hOCvXe2W04PkksHS1g@mail.gmail.com' \
    --to=saurabh.globe@gmail.com \
    --cc=dev@dpdk.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).