From: Zoltan Kiss <zoltan.kiss@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: <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 v4] xen-netback: Fix grant ref resolution in RX path
Date: Thu, 15 May 2014 11:53:10 +0100 [thread overview]
Message-ID: <53749C96.2030102@citrix.com> (raw)
In-Reply-To: <1400150269.4386.30.camel@kazak.uk.xensource.com>
On 15/05/14 11:37, Ian Campbell wrote:
> On Thu, 2014-05-15 at 11:08 +0100, Zoltan Kiss wrote:
>> The original series for reintroducing grant mapping for netback had a patch [1]
>> to handle receiving of packets from an another VIF. Grant copy on the receiving
>> side needs the grant ref of the page to set up the op.
>> The original patch assumed (wrongly) that the frags array haven't changed. In
>> the case reported by Sander, the sending guest sent a packet where the linear
>> buffer and the first frag were under PKT_PROT_LEN (=128) bytes.
>> xenvif_tx_submit() then pulled up the linear area to 128 bytes, and ditched the
>> first frag. The receiving side had an off-by-one problem when gathered the grant
>> refs.
>> This patch fixes that by checking whether the actual frag's page pointer is the
>> same as the page in the original frag list. It can handle any kind of changes on
>> the original frags array, like:
>> - removing granted frags from the array at any point
>> - adding local pages to the frags list anywhere
>> - reordering the frags
>> It's optimized to the most common case, when there is 1:1 relation between the
>> frags and the list, plus works optimal when frags are removed from the end or
>> the beginning.
>>
>> [1]: 3e2234: xen-netback: Handle foreign mapped pages on the guest RX path
>>
>> Reported-by: Sander Eikelenboom <linux@eikelenboom.it>
>> Signed-off-by: Zoltan Kiss <zoltan.kiss@citrix.com>
>
> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>
> (Remind me, do we need both this and Eric's fix, or is it either/or?)
When you say Eric's fix, which one do you talk about? The one for
skb_try_coalesce? That's not too burning, at the moment it is only used
from the IP layer and above, as far as I can tell, and zerocopy skbs get
copied to local pages in deliver_skb.
Zoli
next prev parent reply other threads:[~2014-05-15 10:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 10:08 [PATCH net v4] xen-netback: Fix grant ref resolution in RX path Zoltan Kiss
2014-05-15 10:37 ` Ian Campbell
2014-05-15 10:46 ` Sander Eikelenboom
2014-05-15 10:53 ` Zoltan Kiss [this message]
2014-05-16 3:33 ` David Miller
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=53749C96.2030102@citrix.com \
--to=zoltan.kiss@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.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 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).