All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org
Subject: Re: no hugepage with UIO poll-mode driver
Date: Wed, 25 Nov 2015 11:23:57 +0100	[thread overview]
Message-ID: <1711935.0QY3Nxc9zX@xps13> (raw)
In-Reply-To: <20151125100859.GA3496@bricha3-MOBL3>

2015-11-25 10:08, Bruce Richardson:
> 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.

Even with rte_mem_virt2phy() + rte_mem_lock_page() ?

  reply	other threads:[~2015-11-25 10:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-25  5:45 no hugepage with UIO poll-mode driver Younghwan Go
2015-11-25  6:19 ` Tan, Jianfeng
2015-11-25  6:39   ` Younghwan Go
2015-11-25 10:08     ` Bruce Richardson
2015-11-25 10:23       ` Thomas Monjalon [this message]
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=1711935.0QY3Nxc9zX@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.