From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <xen-devel@lists.xenproject.org>,
<linux-kernel@vger.kernel.org>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
Juergen Gross <jgross@suse.com>,
Patrick Talbert <ptalbert@redhat.com>,
David Vrabel <david.vrabel@citrix.com>
Subject: Re: [PATCH net-next] xen-netfront: avoid packet loss when ethernet header crosses page boundary
Date: Mon, 12 Sep 2016 13:52:17 +0200 [thread overview]
Message-ID: <87sht59vym.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <57D2BC13.8050903@citrix.com> (David Vrabel's message of "Fri, 9 Sep 2016 14:41:39 +0100")
David Vrabel <david.vrabel@citrix.com> writes:
> On 22/08/16 16:42, Vitaly Kuznetsov wrote:
>> Small packet loss is reported on complex multi host network configurations
>> including tunnels, NAT, ... My investigation led me to the following check
>> in netback which drops packets:
>>
>> if (unlikely(txreq.size < ETH_HLEN)) {
>> netdev_err(queue->vif->dev,
>> "Bad packet size: %d\n", txreq.size);
>> xenvif_tx_err(queue, &txreq, extra_count, idx);
>> break;
>> }
>>
>> But this check itself is legitimate. SKBs consist of a linear part (which
>> has to have the ethernet header) and (optionally) a number of frags.
>> Netfront transmits the head of the linear part up to the page boundary
>> as the first request and all the rest becomes frags so when we're
>> reconstructing the SKB in netback we can't distinguish between original
>> frags and the 'tail' of the linear part. The first SKB needs to be at
>> least ETH_HLEN size. So in case we have an SKB with its linear part
>> starting too close to the page boundary the packet is lost.
>>
>> I see two ways to fix the issue:
>> - Change the 'wire' protocol between netfront and netback to start keeping
>> the original SKB structure. We'll have to add a flag indicating the fact
>> that the particular request is a part of the original linear part and not
>> a frag. We'll need to know the length of the linear part to pre-allocate
>> memory.
>> - Avoid transmitting SKBs with linear parts starting too close to the page
>> boundary. That seems preferable short-term and shouldn't bring
>> significant performance degradation as such packets are rare. That's what
>> this patch is trying to achieve with skb_copy().
>>
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>
> We should probably fix the backend to handle this (by grant copying a
> minimum amount in the linear area, but since netfront needs to work with
> older netback.
>
> Acked-by: David Vrabel <david.vrabel@citrix.com>
David,
could you please pick this up for net-next or are there any concerns
remaining?
Thanks,
--
Vitaly
prev parent reply other threads:[~2016-09-12 11:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 15:42 [PATCH net-next] xen-netfront: avoid packet loss when ethernet header crosses page boundary Vitaly Kuznetsov
2016-08-22 16:55 ` [Xen-devel] " David Vrabel
2016-08-23 18:51 ` Vitaly Kuznetsov
2016-08-29 10:28 ` Vitaly Kuznetsov
2016-09-09 13:39 ` Vitaly Kuznetsov
2016-09-09 13:41 ` David Vrabel
2016-09-12 11:52 ` Vitaly Kuznetsov [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=87sht59vym.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=davem@davemloft.net \
--cc=david.vrabel@citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ptalbert@redhat.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).