From: Paolo Abeni <pabeni@redhat.com>
To: pravin shelar <pshelar@ovn.org>
Cc: Jesse Gross <jesse@kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Pravin Shelar <pshelar@nicira.com>,
"David S. Miller" <davem@davemloft.net>,
Flavio Leitner <fbl@sysclose.org>
Subject: Re: [PATCH net] openvswitch: compute needed headroom for internal vports
Date: Wed, 13 Jan 2016 18:30:18 +0100 [thread overview]
Message-ID: <1452706218.28238.2.camel@redhat.com> (raw)
In-Reply-To: <CAOrHB_C0pt9=84t8Jzr1YL5n=Ap2frSy1rBipUqs84mGpg+o3g@mail.gmail.com>
On Tue, 2016-01-12 at 21:27 -0800, pravin shelar wrote:
> On Tue, Jan 12, 2016 at 5:08 PM, Jesse Gross <jesse@kernel.org> wrote:
> > Any traffic coming from the hypervisor itself (as well as tunnels
> > although unless you are doing double encapsulation then this patch
> > doesn't matter in that case).
> >
>
> ok, But majority of traffic comes from VM. So IMO only this patch
> would not make much difference.
>
> > Since we're in the merge window now, maybe it makes sense to just go
> > for the full version in the next cycle in any case.
>
> ok.
Thank you for the feedback.
I'll try to implement a more general solution and get some performance
numbers for the next cycle,
Paolo
prev parent reply other threads:[~2016-01-13 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-08 21:50 [PATCH net] openvswitch: compute needed headroom for internal vports Paolo Abeni
2016-01-08 22:53 ` pravin shelar
2016-01-09 0:42 ` Jesse Gross
2016-01-09 2:44 ` pravin shelar
2016-01-11 8:43 ` Paolo Abeni
2016-01-12 0:34 ` pravin shelar
2016-01-12 19:20 ` Jesse Gross
2016-01-12 20:44 ` pravin shelar
2016-01-13 1:08 ` Jesse Gross
2016-01-13 5:27 ` pravin shelar
2016-01-13 17:30 ` Paolo Abeni [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=1452706218.28238.2.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=fbl@sysclose.org \
--cc=jesse@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
--cc=pshelar@ovn.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).