[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20150629054604.GA2242@nanopsycho.orion>
Date: Mon, 29 Jun 2015 07:46:04 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: Neelakantam Gaddam <neelugaddam@...il.com>
Cc: Thomas Graf <tgraf@...g.ch>, ryazanov.s.a@...il.com,
jasowang@...hat.com, john.r.fastabend@...el.com,
Neil.Jerram@...aswitch.com, edumazet@...gle.com,
andy@...yhouse.net, dev@...nvswitch.org, nbd@...nwrt.org,
f.fainelli@...il.com, ronye@...lanox.com,
jeffrey.t.kirsher@...el.com, ogerlitz@...lanox.com,
ben@...adent.org.uk, buytenh@...tstofly.org,
roopa@...ulusnetworks.com, jhs@...atatu.com, aviadr@...lanox.com,
nicolas.dichtel@...nd.com, vyasevic@...hat.com,
Neil Horman <nhorman@...driver.com>,
Linux Netdev List <netdev@...r.kernel.org>,
stephen@...workplumber.org, dborkman@...hat.com,
ebiederm@...ssion.com, davem@...emloft.net
Subject: Re: [ovs-dev] [patch net-next 00/13] introduce rocker switch driver
with openvswitch hardware accelerated datapath
Mon, Jun 29, 2015 at 07:44:38AM CEST, neelugaddam@...il.com wrote:
>Hi All,
>
>Shall we expect these changes to be available in the upcoming 2.4 release?
>or is it still in development?
Still in devel.
>
>
>
>
>
>
>On Tue, Sep 16, 2014 at 9:28 PM, Jiri Pirko <jiri@...nulli.us> wrote:
>
>> Mon, Sep 08, 2014 at 03:54:13PM CEST, tgraf@...g.ch wrote:
>> >On 09/03/14 at 11:24am, Jiri Pirko wrote:
>> >> This patchset can be divided into 3 main sections:
>> >> - introduce switchdev api for implementing switch drivers
>> >> - add hardware acceleration bits into openvswitch datapath, This uses
>> >> previously mentioned switchdev api
>> >> - introduce rocker switch driver which implements switchdev api
>> >
>> >Jiri, Scott,
>> >
>> >Enclosed is the GOOG doc which outlines some details on my particular
>> >interests [0]. It includes several diagrams which might help to
>> >understand the overall arch. It is highly related to John's work as
>> >well. Please let me know if something does not align with the model
>> >you have in mind.
>>
>>
>> Hi Thomas.
>>
>> Sorry for late answer, I returned from vacation yesterday.
>> I went over your document, I did not find anything which would not align
>> with our approach. Looks good to me.
>>
>> >
>> >Summary:
>> >The full virtual tunnel endpoint flow offload attempts to offload full
>> >flows to the hardware and utilize the embedded switch on the host NIC
>> >to empower the eSwitch with the required flexibility of the software
>> >driven network. In this model, the guest (VM or LXC) attaches through a
>> >SR-IOV VF which serves as the primary path. A slow path / software path
>> >is provided via the CPU which can route packets back into the VF by
>> >tagging packets with forwarding metadata and sending the frame back to
>> >the NIC.
>> >
>> >[0]
>> https://docs.google.com/document/d/195waUliu7G5YYVuXHmLmHgJ38DFSte321WPq0oaFhyU/edit?usp=sharing
>> >(Publicly accessible and open for comments)
>> _______________________________________________
>> dev mailing list
>> dev@...nvswitch.org
>> http://openvswitch.org/mailman/listinfo/dev
>>
>
>
>
>--
>Thanks & Regards
>Neelakantam Gaddam
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists