DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pravin Shelar <pshelar@nicira.com>
To: Vincent JARDIN <vincent.jardin@6wind.com>
Cc: "dev@openvswitch.org" <dev@openvswitch.org>,
	Ben Pfaff <blp@nicira.com>, Jesse Gross <jesse@nicira.com>,
	dev@dpdk.org, dpdk-ovs@lists.01.org
Subject: Re: [dpdk-dev] [PATCH RFC] dpif-netdev: Add support Intel DPDK based ports.
Date: Wed, 29 Jan 2014 11:32:34 -0800	[thread overview]
Message-ID: <CALnjE+o5hhYiqhduySq+Ywyz_CQJ3XJ2Tku-SstXoj+stL4RNA@mail.gmail.com> (raw)
In-Reply-To: <52E8482D.10804@6wind.com>

On Tue, Jan 28, 2014 at 4:15 PM, Vincent JARDIN
<vincent.jardin@6wind.com> wrote:
> Hi Pravin,
>
>
>>> Few feature questions:
>>>
>>>    - what's about the vNIC supports (toward the guests)?
>>>    - what's about IPsec support (VxLAN over IPsec for instance)?
>>> I do not understand how your patch will solve those 2 cases.
>>>
>> At this point I wanted to get basic DPDK support in OVS, once that is
>> done we can add support for vNIC.
>
>
> For vNIC, did you notice:
>   http://dpdk.org/browse/memnic/
>
> ?

AFAIU it is introducing backend driver for vNIC which shld work with this patch.

>
>> IPsec and vxlan or any L3 tunneling requires IP stack in userspace and
>> needs more design work.
>
>
> OK, understood.
>
>
>>>>>> This is based a patch from Gerald Rogers.
>>>
>>>
>>> Please which patch? I cannot find it into the archives.
>>>
>> It was directly sent to Jesse at Nicira. If you want I can send it out for
>> ref.
>
>
> Yes, please.

Attached is the patch based upon HEAD-309d9da.

Thanks,
Pravin.

>
> Thank you,
>   Vincent
>

  reply	other threads:[~2014-01-29 19:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-28  1:48 pshelar
     [not found] ` <20140128044950.GA4545@nicira.com>
2014-01-28  5:28   ` [dpdk-dev] [ovs-dev] " Pravin Shelar
2014-01-28 14:47     ` [dpdk-dev] " Vincent JARDIN
2014-01-28 17:56       ` Pravin Shelar
2014-01-29  0:15         ` Vincent JARDIN
2014-01-29 19:32           ` Pravin Shelar [this message]
     [not found]       ` <52E7D2A8.400@redhat.com>
2014-01-28 18:20         ` [dpdk-dev] [ovs-dev] " Pravin Shelar
     [not found] ` <52E7D13B.9020404@redhat.com>
2014-01-28 18:17   ` Pravin Shelar
2014-01-29  8:15     ` Thomas Graf
2014-01-29 10:26       ` Vincent JARDIN
2014-01-29 11:14         ` Thomas Graf
2014-01-29 16:34           ` Vincent JARDIN
2014-01-29 17:14             ` Thomas Graf
2014-01-29 18:42               ` Stephen Hemminger
2014-01-29 20:47               ` François-Frédéric Ozog
2014-01-29 23:15                 ` Thomas Graf
2014-03-13  7:37                 ` David Nyström
2014-01-29  8:56 ` [dpdk-dev] " Prashant Upadhyaya
2014-01-29 21:29   ` Pravin Shelar
2014-01-30 10:15     ` Prashant Upadhyaya
2014-01-30 16:27       ` Rogers, Gerald
2014-01-29 10:01 ` [dpdk-dev] [ovs-dev] " Thomas Graf
2014-01-29 21:49   ` Pravin Shelar

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=CALnjE+o5hhYiqhduySq+Ywyz_CQJ3XJ2Tku-SstXoj+stL4RNA@mail.gmail.com \
    --to=pshelar@nicira.com \
    --cc=blp@nicira.com \
    --cc=dev@dpdk.org \
    --cc=dev@openvswitch.org \
    --cc=dpdk-ovs@lists.01.org \
    --cc=jesse@nicira.com \
    --cc=vincent.jardin@6wind.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).