From: Bruce Richardson <bruce.richardson@intel.com>
To: Younghwan Go <yhwan@ndsl.kaist.edu>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] no hugepage with UIO poll-mode driver
Date: Wed, 25 Nov 2015 10:08:59 +0000 [thread overview]
Message-ID: <20151125100859.GA3496@bricha3-MOBL3> (raw)
In-Reply-To: <56555795.60408@ndsl.kaist.edu>
On Wed, Nov 25, 2015 at 03:39:17PM +0900, Younghwan Go wrote:
> Hi Jianfeng,
>
> Thanks for the email. rte mempool was successfully created without any
> error. Now the next problem is that rte_eth_rx_burst() is always returning 0
> as if there was no packet to receive... Do you have any suggestion on what
> might be causing this issue? In the meantime, I will be digging through
> ixgbe driver code to see what's going on.
>
> Thank you,
> Younghwan
>
The problem is that with --no-huge we don't have the physical address of the memory
to write to the network card. That's what it's marked as for testing only.
/Bruce
> 2015-11-25 오후 3:19에 Tan, Jianfeng 이(가) 쓴 글:
> >Hi Younghwan
> >When you specify --no-huge, by default, only 64M memory is used. Can you use -m 1024 to
> >Mmap 1G memory to have a try?
> >
> >Jianfeng
> >
> >>-----Original Message-----
> >>From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Younghwan Go
> >>Sent: Wednesday, November 25, 2015 1:46 PM
> >>To: dev@dpdk.org
> >>Subject: [dpdk-dev] no hugepage with UIO poll-mode driver
> >>
> >>Hello,
> >>
> >>I'm trying to create rte mempool with my own memory scheme (shared
> >>virtual memory between CPU & GPU) other than using hugepage. I'm using
> >>IGB UIO module with Ethernet 10G 2P X520 Adapter NIC.
> >>
> >>I first tried to disable hugepage by inserting "--no-huge" option, but it gave
> >>an error at rte_mempool_create function. Then I found in rte_eal.h file that
> >>said "no-huge mode cannot be used with UIO poll-mode drivers like
> >>igb/ixgbe".
> >>
> >>Is there a way to switch DPDK code to not use hugepage with ixgbe driver or
> >>is it not possible to do so?
> >>
> >>Thank you,
> >>Younghwan
>
next prev parent reply other threads:[~2015-11-25 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 5:45 Younghwan Go
2015-11-25 6:19 ` Tan, Jianfeng
2015-11-25 6:39 ` Younghwan Go
2015-11-25 10:08 ` Bruce Richardson [this message]
2015-11-25 10:23 ` Thomas Monjalon
2015-11-25 11:00 ` Bruce Richardson
2015-11-25 11:03 ` Thomas Monjalon
2015-11-25 12:02 ` Bruce Richardson
2015-11-25 13:22 ` Thomas Monjalon
2015-11-25 13:44 ` Sergio Gonzalez Monroy
2015-11-25 14:12 ` Ananyev, Konstantin
2015-11-26 4:47 ` Younghwan Go
2015-11-26 14:37 ` Kyle Larose
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=20151125100859.GA3496@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=yhwan@ndsl.kaist.edu \
/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).