From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xen.org, netdev@vger.kernel.org
Cc: annie.li@oracle.com, david.vrabel@citrix.com,
ian.campbell@citrix.com, konrad.wilk@oracle.com
Subject: [PATCH 0/6 V2] Bundle fixes for Xen netfront / netback
Date: Mon, 25 Mar 2013 11:08:16 +0000 [thread overview]
Message-ID: <1364209702-12437-1-git-send-email-wei.liu2__38879.9322340221$1364209869$gmane$org@citrix.com> (raw)
1, 3 and 4 are just mechanical fixes to make code cleaner.
2 fixes the bug that netfront generates oversize skbs. The fix was suggested by
Ben. My test shows that netfront doesn't generate oversize skb after this fix.
4 tries to coalesce slots before copying. This version enlarges the grant copy
buffer to avoid overflow.
6 loosens the punishment when netback sees oversize packet.
Wei.
next reply other threads:[~2013-03-25 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 11:08 Wei Liu [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-25 11:08 [PATCH 0/6 V2] Bundle fixes for Xen netfront / netback Wei Liu
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='1364209702-12437-1-git-send-email-wei.liu2__38879.9322340221$1364209869$gmane$org@citrix.com' \
--to=wei.liu2@citrix.com \
--cc=annie.li@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=netdev@vger.kernel.org \
--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.