From: "Zhou, Danny" <danny.zhou@intel.com>
To: Karmarkar Suyash <skarmarkar@sonusnet.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Running DPDK with Docker
Date: Wed, 1 Apr 2015 23:08:49 +0000 [thread overview]
Message-ID: <DFDF335405C17848924A094BC35766CF0AB3E37F@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <BY1PR03MB1338CC2057D20920542AACDDB3F30@BY1PR03MB1338.namprd03.prod.outlook.com>
DPDK 2.0 support uio_pci_geneic this in_kernel module so you do not need to insmod igb_uio, and rte_kni module can hardly been
upstreamed to net_dev, but it is not a must-to-have module to load if you do not use KNI feaure.
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Karmarkar Suyash
> Sent: Thursday, April 02, 2015 1:57 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] Running DPDK with Docker
>
> Hi,
>
> Given the popularity of Docker it would be nice if we can run DPDK inside a Docker container but the challenge is the igb_uio.ko
> and rte_kni.ko kernel modules which need to be compiled with the exact kernel source running on the host. Are there ways to
> seamlessly run DPDK with Docker? I came across an articles about running DPDK with Linux container but still the requirement is to
> insert igb_uio. Any plans to make the igb_uio and rte_kni modules as default modules of Linux source code or any other better
> approaches/suggestions ? Thanks.
>
> http://dpdk.org/ml/archives/dev/2014-October/006373.html
> http://permalink.gmane.org/gmane.comp.networking.dpdk.devel/6479
>
>
> Regards
> Suyash Karmarkar
prev parent reply other threads:[~2015-04-01 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 17:56 Karmarkar Suyash
2015-04-01 18:41 ` Stephen Hemminger
2015-04-02 3:28 ` Karmarkar Suyash
2015-04-02 6:36 ` Andre Richter
2015-04-02 7:13 ` Zhou, Danny
2015-04-01 23:08 ` Zhou, Danny [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=DFDF335405C17848924A094BC35766CF0AB3E37F@SHSMSX104.ccr.corp.intel.com \
--to=danny.zhou@intel.com \
--cc=dev@dpdk.org \
--cc=skarmarkar@sonusnet.com \
/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).