From: "Jacek Milewicz" <jacekowski@jacekowski.org>
To: 'Wei Liu' <wei.liu2@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: bug disabling guest interface
Date: Wed, 6 Mar 2013 19:34:44 +0100 (CET) [thread overview]
Message-ID: <024b01ce1a99$43b1fe60$cb15fb20$@jacekowski.org> (raw)
In-Reply-To: <1362593840.29093.38.camel@zion.uk.xensource.com>
> I'm interested in knowing more information. Have you always been using
> MAX_SKB_FRAGS > default_value (16 or 17) for you DomUs?
18 used to be default value on older kernels (anything older than
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/include/linux/skbuff.h?id=9d4dde5215779f4099730194ad30624fdba3d8b2 -
2011-12-23 21:51:18)
> If it is this case, you're likely to be hitting this error path all the
> time. It is just
> that XSA-39 chooses to shutdown vif if there is something wrong. So my
> further questions is, do you notice any performance problem in the case
> that
> netback silently drops your packets?
Basically what happened in our case is VMs were migrated to new host with
new kernel, before that dom0 used to run kernel with MAX_SKB_FRAGS==18 so it
was same for both dom0 and domU.
New host has kernel with XSA-39 fixes and smaller MAX_SKB_FRAGS (17), and
that's when we encountered that bug, we've never tried kernel with smaller
MAX_SKB_FRAGS but without XSA_39 fix.
next prev parent reply other threads:[~2013-03-06 18:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-05 22:51 bug disabling guest interface Jacek Milewicz
2013-03-06 18:17 ` Wei Liu
2013-03-06 18:34 ` Jacek Milewicz [this message]
2013-03-06 21:03 ` Teck Choon Giam
-- strict thread matches above, loose matches on Subject: below --
2013-03-08 8:46 Steven Haigh
2013-03-08 19:36 ` Jacek Milewicz
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='024b01ce1a99$43b1fe60$cb15fb20$@jacekowski.org' \
--to=jacekowski@jacekowski.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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.