From: Zoltan Kiss <zoltan.kiss@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
<xen-devel@lists.xenproject.org>, <wei.liu2@citrix.com>,
<linux@eikelenboom.it>, <paul.durrant@citrix.com>,
<netdev@vger.kernel.org>, <david.vrabel@citrix.com>,
<davem@davemloft.net>
Subject: Re: [PATCH net RFC] xen-netback: Fix grant ref resolution in RX path
Date: Wed, 14 May 2014 19:44:04 +0100 [thread overview]
Message-ID: <5373B974.6050808@citrix.com> (raw)
In-Reply-To: <1400085639.26934.17.camel@kazak.uk.xensource.com>
On 14/05/14 17:40, Ian Campbell wrote:
>
> On Wed, 2014-05-14 at 14:25 +0100, Zoltan Kiss wrote:
>
>> But of course it should be carefully checked that functions which place
>> frags into another frags arrays should call orphan_frags, e.g. I guess
>> skb_shift does such thing. That's what I intend to start another thread
>> about.
>
> I see Eric has posted a fix for skb_try_coalesce(), but is that likely
> to be acceptable for 3.15? How many other similar patches are we
> expecting and/or how long do you think this careful checking will take?
>
> Given that we are now at 3.15-rc5 I think we need to decide how to
> proceed, either push ahead fixing all these issues or (partially) revert
> this netback feature and try again for 3.16.
I guess these problems apply to KVM as well, and it haven't caused them
problem so far, so I guess the problem shouldn't be that big. I assume
they are using this feature to send fragmented skbs out from a guest,
but I might be wrong.
Anyway, I think I'll check tomorrow if there are further places to worry
about, but I don't think if there are any of them which are easily
reproducible.
Zoli
next prev parent reply other threads:[~2014-05-14 18:44 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 14:31 [PATCH net RFC] xen-netback: Fix grant ref resolution in RX path Zoltan Kiss
2014-05-13 15:47 ` Ian Campbell
2014-05-13 20:18 ` Zoltan Kiss
2014-05-13 20:18 ` Zoltan Kiss
2014-05-13 15:47 ` Ian Campbell
2014-05-13 16:13 ` Eric Dumazet
2014-05-13 16:13 ` Eric Dumazet
2014-05-13 19:25 ` Sander Eikelenboom
2014-05-13 19:25 ` Sander Eikelenboom
2014-05-14 8:32 ` Ian Campbell
2014-05-14 13:37 ` David Vrabel
2014-05-14 13:37 ` David Vrabel
2014-05-14 8:32 ` Ian Campbell
2014-05-14 11:12 ` Zoltan Kiss
2014-05-14 11:12 ` Zoltan Kiss
2014-05-14 11:35 ` Eric Dumazet
2014-05-14 13:25 ` Zoltan Kiss
2014-05-14 16:40 ` Ian Campbell
2014-05-14 16:40 ` Ian Campbell
2014-05-14 17:28 ` Sander Eikelenboom
2014-05-14 17:28 ` Sander Eikelenboom
2014-05-14 18:44 ` Zoltan Kiss [this message]
2014-05-15 8:41 ` Ian Campbell
2014-05-15 8:41 ` Ian Campbell
2014-05-14 18:44 ` Zoltan Kiss
2014-05-14 13:25 ` Zoltan Kiss
2014-05-14 11:35 ` Eric Dumazet
2014-05-15 8:31 ` Ian Campbell
2014-05-15 8:31 ` Ian Campbell
2014-05-15 10:14 ` Zoltan Kiss
2014-05-15 10:14 ` Zoltan Kiss
-- strict thread matches above, loose matches on Subject: below --
2014-05-13 14:31 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=5373B974.6050808@citrix.com \
--to=zoltan.kiss@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.com \
--cc=eric.dumazet@gmail.com \
--cc=linux@eikelenboom.it \
--cc=netdev@vger.kernel.org \
--cc=paul.durrant@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 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.