From mboxrd@z Thu Jan 1 00:00:00 1970 From: James Harper Subject: Re: xennet: skb rides the rocket: 20 slots Date: Tue, 8 Jan 2013 20:57:19 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B35598AD6@BITCOM1.int.sbss.com.au> References: <72958707.20130104172854@eikelenboom.it> <1357556115.7989.13.camel@zakaz.uk.xensource.com> <50EB8091.90705@oracle.com> <1357639549.7989.147.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1357639549.7989.147.camel@zakaz.uk.xensource.com> Content-Language: en-US List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell , ANNIE LI Cc: Sander Eikelenboom , xen-devel , Konrad Rzeszutek Wilk List-Id: xen-devel@lists.xenproject.org > > If netback complains about "Too many frags", then it should be > > MAX_SKB_FRAGS limitation in netback results in dropping packets in > > netfront. It is possible that other netfronts(windows?) also hit this. > > It's very possible. I rather suspect that non-Linux frontends have > workarounds (e.g. manual resegmenting etc) for this case. > GPLPV gathers fragments together if there are too many. Mostly this is just the header but there could be a whole lot of copying going on in a worst-case packet. It would be nice if a max-frags value was written to xenstore... do different backends (solaris? Bsd?) have different requirements? Or maybe that's already been discussed - I haven't followed this thread closely. James