From: David Miller <davem@davemloft.net>
To: borntraeger@de.ibm.com
Cc: vyasevic@redhat.com, netdev@vger.kernel.org, mst@redhat.com,
mjrosato@linux.vnet.ibm.com, jasowang@redhat.com
Subject: Re: Performance regression 3.11 with macvlan between 2 linux guests (bisected)
Date: Thu, 22 Aug 2013 01:29:56 -0700 (PDT) [thread overview]
Message-ID: <20130822.012956.317193234029192175.davem@davemloft.net> (raw)
In-Reply-To: <5215CA84.8070906@de.ibm.com>
From: Christian Borntraeger <borntraeger@de.ibm.com>
Date: Thu, 22 Aug 2013 10:23:32 +0200
> On 21/08/13 20:12, Vlad Yasevich wrote:
>
>>>
>>> A corrected patch has been sent upstream. We take into consideration
>>> the features on the target device that the user/vm has specified.
>>> If the VM has enabled the TSO flags, then nothing will happen to the
>>> GSO packet. However, if the TSO flag is off, segmentation will be
>>> performed.
>>
>> Particularly. This commit should fix the issue:
>> commit a567dd6252263c8147b7269df5d03d9e31463e11
>> macvtap: simplify usage of tap_features
>
> Tested-by: Christian Borntraeger <borntraeger@de.ibm.com>
>
> The patch is still in net.git, but not in Linus git. Are we going to push this
> for 3.11?
Of course. Anything in 'net' is intended to make it into Linus's tree.
I generally push things to Linus every week or two.
prev parent reply other threads:[~2013-08-22 8:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 12:38 Performance regression 3.11 with macvlan between 2 linux guests (bisected) Christian Borntraeger
2013-08-21 18:04 ` Vlad Yasevich
2013-08-21 18:12 ` Vlad Yasevich
2013-08-22 8:23 ` Christian Borntraeger
2013-08-22 8:29 ` David Miller [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=20130822.012956.317193234029192175.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=borntraeger@de.ibm.com \
--cc=jasowang@redhat.com \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.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).