DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: XU Liang <liang.xu@cinfotech.cn>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: map uio resources after hugepages when --base_virtaddr is configured
Date: Wed, 05 Nov 2014 11:38:23 +0100	[thread overview]
Message-ID: <1425866.EsRhEH6Yif@xps13> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D897268330EA@IRSMSX108.ger.corp.intel.com>

The patch was attached and automatically dropped.
Please follow these guidelines:
	http://dpdk.org/dev#send

2014-11-05 09:58, De Lara Guarch, Pablo:
> Patch is missing. 
> 
> Thanks,
> Pablo
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of XU Liang
> > Sent: Wednesday, November 05, 2014 9:50 AM
> > To: dev
> > Subject: [dpdk-dev] [PATCH] eal: map uio resources after hugepages when --
> > base_virtaddr is configured
> > 
> > 
> > When start a secondary process, we got error message "EAL:
> > pci_map_resource(): cannot mmap(11, 0x7ffff7fba000, 0x20000, 0x0): Bad
> > file descriptor (0x7ffff7fb9000)"
> > 
> > The secondary process link difference shared libraries, so the 0x7ffff7fba000
> > is used.
> > 
> > We know the --base_virtaddr is designed for this situation for hugepages.
> > 
> > This patch map the device resouce into address that is after hugepages when
> > --base_virtaddr is  configured.

      reply	other threads:[~2014-11-05 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-05  9:49 XU Liang
2014-11-05  9:58 ` De Lara Guarch, Pablo
2014-11-05 10:38   ` Thomas Monjalon [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=1425866.EsRhEH6Yif@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=liang.xu@cinfotech.cn \
    /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).