lkml.org 
[lkml]   [2013]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [Xen-devel] [PATCH net-next RFC 3/5] xen-netback: Remove old TX grant copy definitons
On 30/10/13 09:39, Jan Beulich wrote:
>>>> On 30.10.13 at 01:50, Zoltan Kiss <zoltan.kiss@citrix.com> wrote:
>> These became obsolate with grant mapping.
>
> I didn't look at this in detail, but I'm surprised you can get away
> without any copying: For one, the header part needs copying
> anyway, so you'd pointlessly map and then copy it if it's small
> enough.
Yep, that's a further plan for optimization. I think I will add that as
a separate patch to the series later. But that doesn't necessarily needs
these definitions, let's see that later.

> And second you need to be prepared for the frontend
> to hand you more slots than you can fit in MAX_SKB_FRAGS
> (namely when MAX_SKB_FRAGS < XEN_NETIF_NR_SLOTS_MIN),
> which you can't handle with mapping alone afaict.
Oh, I was not aware of this problem. And indeed, the trivial solution is
to keep the grant copy methods for such kind of packets, however that
sounds quite nasty.
My another idea is to use skb_shinfo(skb)->frag_list for such packets,
so the stack will see it as a fragmented IP packet. It might be less
efficient than coalescing them into one skb during grant copy at first
place, but probably a cleaner solution. If we don't care that much about
the performance of such guests, it might be a better solution.
But I don't know that closely the IP fragmentation ideas, so it might be
a bad idea. I'm happy to hear comments from people who have more
experience with that.

Zoli


\
 
 \ /
  Last update: 2013-10-31 21:01    [W:0.150 / U:0.672 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site