From: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
To: Aniraj Kesavan <anirajkesavan@gmail.com>
Cc: Andriy Berestovskyy <aber@semihalf.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] Need help understanding rte_eth_dev_count
Date: Thu, 13 Oct 2016 11:17:36 +0500 [thread overview]
Message-ID: <CAN7yQ2oLFSNDeftiZ0PkxhvDpiD3i5abz7OGmqsjzimuYoVoHg@mail.gmail.com> (raw)
In-Reply-To: <CAFOf+QV4t0EuZkcX+s4vc78ebZGtY_D2-7yqCjNf66pp0r54wg@mail.gmail.com>
kindly keep the basic command the same and u can change the number of
hugepages from 64 to ur liking, do that and respond with results
kindly
prev parent reply other threads:[~2016-10-13 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 4:44 Aniraj Kesavan
[not found] ` <CAOysbxpmme2xHxi5SVUi1ZO3KDz+jWvsu_7b_AmMmXNHrkRO3g@mail.gmail.com>
2016-10-12 17:47 ` Aniraj Kesavan
2016-10-13 6:01 ` Muhammad Zain-ul-Abideen
2016-10-13 6:12 ` Aniraj Kesavan
2016-10-13 6:17 ` Muhammad Zain-ul-Abideen [this message]
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=CAN7yQ2oLFSNDeftiZ0PkxhvDpiD3i5abz7OGmqsjzimuYoVoHg@mail.gmail.com \
--to=zain2294@gmail.com \
--cc=aber@semihalf.com \
--cc=anirajkesavan@gmail.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).