From: Steven Haigh <netwiz@crc•id.au>
To: David Vrabel <david.vrabel@citrix•com>
Cc: netdev@vger•kernel.org, xen-devel@lists•xen.org
Subject: Re: [3.15-rc3] Bisected: xen-netback mangles packets between two guests on a bridge since merge of "TX grant mapping with SKBTX_DEV_ZEROCOPY instead of copy" series.
Date: Fri, 16 May 2014 12:13:45 +1000 [thread overview]
Message-ID: <53757459.4030107@crc.id.au> (raw)
In-Reply-To: <5369EBF9.20304@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On 07/05/14 18:16, David Vrabel wrote:
> On 06/05/14 19:07, Steven Haigh wrote:
>> Well, I'm trying to get a test together - although I don't have webdav
>> anywhere... I was going to try it via FTP, however I'm hitting another
>> MM bug in Xen:
>> https://bugs.archlinux.org/task/38596
>>
>> This references:
>> https://lkml.org/lkml/2014/1/23/596
>>
>> It says that should be fixed in 3.15-rc3 (if I understand properly) -
>> but I'm also hitting that on 3.14.2. Did these changes get ported back
>> to the 3.14 tree?
>
> This is fixed by 29c7787075 (mm: use paravirt friendly ops for NUMA
> hinting ptes) which is tagged for stable but hasn't yet been picked up
> for 3.14.y.
>
> You can also work around it by disabling CONFIG_NUMA_BALANCING which
> doesn't work with Xen PV guests anyway.
Hi David,
Just wondering if there has been any movement in getting this into
3.14.y. I see we've now just hit 3.14.4 with no mention of the patch for
issue.
--
Steven Haigh
Email: netwiz@crc•id.au
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-16 2:13 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 10:45 [3.15-rc3] Bisected: xen-netback mangles packets between two guests on a bridge since merge of "TX grant mapping with SKBTX_DEV_ZEROCOPY instead of copy" series Sander Eikelenboom
2014-04-30 15:24 ` Eric Dumazet
2014-04-30 20:40 ` Zoltan Kiss
2014-04-30 20:53 ` Zoltan Kiss
2014-04-30 22:25 ` Sander Eikelenboom
2014-05-01 13:37 ` Zoltan Kiss
2014-05-01 13:59 ` Sander Eikelenboom
2014-05-01 15:46 ` Zoltan Kiss
2014-05-01 17:39 ` Sander Eikelenboom
2014-05-01 17:46 ` Eric Dumazet
2014-05-01 19:39 ` [Xen-devel] " Sander Eikelenboom
2014-05-02 14:00 ` Zoltan Kiss
2014-05-02 14:06 ` Sander Eikelenboom
2014-05-02 14:47 ` Zoltan Kiss
2014-05-02 15:21 ` Eric Dumazet
2014-05-02 15:26 ` Zoltan Kiss
2014-05-02 16:28 ` Sander Eikelenboom
2014-05-02 16:45 ` Zoltan Kiss
2014-05-05 10:19 ` Sander Eikelenboom
2014-05-06 17:07 ` Steven Haigh
2014-05-06 17:13 ` Zoltan Kiss
2014-05-06 17:37 ` Sander Eikelenboom
2014-05-06 18:07 ` Steven Haigh
2014-05-07 8:16 ` [Xen-devel] " David Vrabel
2014-05-16 2:13 ` Steven Haigh [this message]
2014-05-06 17:08 ` Zoltan Kiss
2014-05-06 17:10 ` Zoltan Kiss
2014-05-06 17:33 ` Sander Eikelenboom
2014-05-01 13:49 ` Zoltan Kiss
2014-05-01 14:05 ` Sander Eikelenboom
2014-05-01 15:16 ` Zoltan Kiss
2014-05-01 15:40 ` Sander Eikelenboom
2014-05-02 15:35 ` Eric Dumazet
2014-05-02 22:18 ` Sander Eikelenboom
2014-05-09 22:19 ` Neal Cardwell
2014-05-09 21:02 ` Zoltan Kiss
2014-05-13 13:40 ` Zoltan Kiss
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=53757459.4030107@crc.id.au \
--to=netwiz@crc$(echo .)id.au \
--cc=david.vrabel@citrix$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=xen-devel@lists$(echo .)xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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