All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent JARDIN <vincent.jardin@6wind.com>
To: Jesse Gross <jesse@nicira.com>, Tom Herbert <therbert@google.com>
Cc: Pravin Shelar <pshelar@nicira.com>,
	David Miller <davem@davemloft.net>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 0/3] openvswitch: Add STT support.
Date: Thu, 22 Jan 2015 00:46:31 +0100	[thread overview]
Message-ID: <54C03A57.4080002@6wind.com> (raw)
In-Reply-To: <CAEP_g=_B5xTcfONUP4PTw91PdJKx_cN_+Qdd4F6300aXVyzLZg@mail.gmail.com>

Jesse, Tom,

On 21/01/2015 23:14, Jesse Gross wrote:
>> I'm not going to try to draw conclusions from data which is obviously
>> >biased and incomplete. If you want to move forward on this, then just
>> >provide network interface for STT so we can independently run our own
>> >comparisons against other encapsulations like we've been doing all
>> >along.
> You have the source code, so you are totally free to run whatever
> tests you like to draw your own conclusions. Personally, I find a more
> than doubling of performance in the environments that I have seen
> compelling. Your mileage may vary.

+1 for STT in the kernel:
   - whatever the performances, it is needed because it happened to be 
used. If the patch can be optimized, someone will do and provide the 
related patches. The patch from Pravin is ok but...

   - ...I agree with Tom, a netdevice is a must have to ack't this 
patch. Such feature should not be added into openvswitch without its 
counter-part netdevice.

thank you,
   Vincent

  reply	other threads:[~2015-01-21 23:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 20:25 [PATCH net-next 0/3] openvswitch: Add STT support Pravin B Shelar
2015-01-20 23:06 ` Tom Herbert
2015-01-21  9:08   ` Pravin Shelar
2015-01-21 16:51     ` Tom Herbert
2015-01-21 18:30       ` Pravin Shelar
2015-01-21 19:45         ` Tom Herbert
2015-01-21 20:22           ` Eric Dumazet
2015-01-21 20:35           ` Jesse Gross
2015-01-21 21:54             ` Tom Herbert
2015-01-21 22:14               ` Jesse Gross
2015-01-21 23:46                 ` Vincent JARDIN [this message]
2015-01-22 16:24                   ` Tom Herbert
2015-01-22 17:51                     ` Vincent JARDIN
2015-01-23  9:04                       ` David Miller
2015-01-23  9:00                     ` David Miller
2015-02-02 16:23             ` Tom Herbert
2015-02-02 20:39               ` Jesse Gross
2015-02-02 22:49                 ` Tom Herbert
2015-01-23 16:58 ` Tom Herbert
2015-01-23 17:38   ` Jesse Gross
2015-01-23 18:25     ` Tom Herbert
2015-01-23 20:20       ` Jesse Gross
2015-01-23 20:57         ` Tom Herbert
2015-01-23 21:11           ` Pravin Shelar
2015-02-02 16:15         ` Tom Herbert

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=54C03A57.4080002@6wind.com \
    --to=vincent.jardin@6wind.com \
    --cc=davem@davemloft.net \
    --cc=jesse@nicira.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@nicira.com \
    --cc=therbert@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.