DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Abdul Rasheed Shaik <ABDUL.RASHEED@LNTTECHSERVICES.COM>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Error in compiling Intel DPDK in FreeBSD with IVSHMEM
Date: Wed, 27 Aug 2014 11:22:29 +0100	[thread overview]
Message-ID: <20140827102229.GB10966@sivswdev02.ir.intel.com> (raw)
In-Reply-To: <20FA96CBE1A24D4191A5EABB5763AB0BBB33B4@POCITMSEXMB06.LntUniverse.com>

On Wed, Aug 27, 2014 at 08:13:59AM +0000, Abdul Rasheed Shaik wrote:
> 
> Hello,
> 
> DPDK doesnt compile with MACHINE---> ivshmem.
> 
> I tried to compile DPDK on FreeBSD Guest machine.
> gmake install T=x86_64-ivshmem-bsdapp-gcc CC=gcc48
> I get the following error
> ,,,
> ,,,
> Build app
> Build app/test
> CC test_ivshmem.o
> /root/dpdk-1.7.0/app/test/test_ivshmem.c:49:25: fatal error:rte_ivshmem.h:No such file or directory
> #include
> ^
> compilation terminated.
> 
> Created a new target environment using the following:
> cp config/defconfig_x86_64-ivshmem-linuxapp-gcc config/defconfig_x86_64-ivshmem-bsdapp-gcc
> 
> Please let me know if there is support in FreeBSD to compile with TARGET as x86_64-ivshmem-bsdapp-gcc.
>

This is not something that is currently supported, as it relies upon a specific way of setting up the memory. Memory setup is very different on BSD vs Linux - Linux targets use the hugetlbfs filesystem, while BSD ones rely on a separate kernel module to reserve large blocks of memory from the kernel at boot time.
 
> Thanks & Regards,
> Abdul Rasheed
> 
> L&T Technology Services Ltd
> 
> www.LntTechservices.com<http://www.lnttechservices.com/>
> 
> This Email may contain confidential or privileged information for the intended recipient (s). If you are not the intended recipient, please do not use or disseminate the information, notify the sender and delete it from your system.

      reply	other threads:[~2014-08-27 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AF3245DCB905C54DAE127D81D2B5B2EE2AF753@POCITMSEXMB06.LntUniverse.com>
     [not found] ` <AF3245DCB905C54DAE127D81D2B5B2EE2AF7FD@POCITMSEXMB06.LntUniverse.com>
     [not found]   ` <20FA96CBE1A24D4191A5EABB5763AB0BBB32F0@POCITMSEXMB06.LntUniverse.com>
     [not found]     ` <20FA96CBE1A24D4191A5EABB5763AB0BBB3367@POCITMSEXMB06.LntUniverse.com>
2014-08-27  8:13       ` Abdul Rasheed Shaik
2014-08-27 10:22         ` Bruce Richardson [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=20140827102229.GB10966@sivswdev02.ir.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=ABDUL.RASHEED@LNTTECHSERVICES.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 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).