Re: [dpdk-dev] no hugepage with UIO poll-mode driver

[Bruce Richardson <bruce.richardson@intel.com>]

On Wed, Nov 25, 2015 at 11:23:57AM +0100, Thomas Monjalon wrote:
> 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() ?
> 
With no-huge, we just set up a single memory segment at startup and set its
"physaddr" to be the virtual address.

/Bruce

        /* hugetlbfs can be disabled */
        if (internal_config.no_hugetlbfs) {
                addr = mmap(NULL, internal_config.memory, PROT_READ | PROT_WRITE,
                                MAP_PRIVATE | MAP_ANONYMOUS, 0, 0);
                if (addr == MAP_FAILED) {
                        RTE_LOG(ERR, EAL, "%s: mmap() failed: %s\n", __func__,
                                        strerror(errno));
                        return -1;
                }
                mcfg->memseg[0].phys_addr = (phys_addr_t)(uintptr_t)addr;
                mcfg->memseg[0].addr = addr;
                mcfg->memseg[0].hugepage_sz = RTE_PGSIZE_4K;
                mcfg->memseg[0].len = internal_config.memory;
                mcfg->memseg[0].socket_id = 0;
                return 0;
        }