From: yue <ooolinux@163.com>
To: Digimer <linux@alteeve.com>
Cc: xen-devel@lists.xensource.com
Subject: Re:Patches to enable MTUs >1500 in el5.6 ready for testing.
Date: Sat, 23 Apr 2011 09:40:58 +0800 (CST) [thread overview]
Message-ID: <a7bbf1.1367.12f8004557b.Coremail.ooolinux@163.com> (raw)
In-Reply-To: <4DB212F6.8020805@alteeve.com>
[-- Attachment #1.1: Type: text/plain, Size: 1079 bytes --]
if the patch will be merged in mainline?
how to get the patch?
thanks
At 2011-04-23 07:44:54，Digimer <linux@alteeve.com> wrote:
>Hi all,
>
> With help from others, I've been able to get Olaf's patch for enabling
>MTUs >1500 for vifX.y and tapZ devices working. I've been able to boot
>dom0, launch domU and live-migrate without having the bridge's MTU
>degrade at any time.
>
> Would the Xen RPM maintainers (and others) mind taking a look at the
>following patches?
>
>Kernel part:
>https://bugzilla.redhat.com/show_bug.cgi?id=697021
>
>Scripts part:
>https://bugzilla.redhat.com/show_bug.cgi?id=697310
>
> I've tested these on systems with stock MTUs of 1500 and they didn't
>cause me any troubles.
>
> If they can be tested and/or signed off on for the next round of RPMs,
>I'd be very grateful. :)
>
>--
>Digimer
>E-Mail: digimer@alteeve.com
>AN!Whitepapers: http://alteeve.com
>Node Assassin: http://nodeassassin.org
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel
[-- Attachment #1.2: Type: text/html, Size: 2005 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-04-23 1:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 23:44 Patches to enable MTUs >1500 in el5.6 ready for testing Digimer
2011-04-23 1:40 ` yue [this message]
2011-04-23 2:31 ` Digimer
2011-04-23 2:38 ` Digimer
2011-04-23 17:42 ` Pasi Kärkkäinen
2011-04-23 18:29 ` Ian Campbell
2011-04-23 21:52 ` Digimer
2011-04-24 6:47 ` Ian Campbell
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=a7bbf1.1367.12f8004557b.Coremail.ooolinux@163.com \
--to=ooolinux@163.com \
--cc=linux@alteeve.com \
--cc=xen-devel@lists.xensource.com \
/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).