All of lore.kernel.org
 help / color / mirror / Atom feed
From: Madison Kelly <mkelly@iplink.net>
To: xen-devel@lists.xensource.com
Subject: Patches to enable MTUs >1500 in el5.6 ready for testing.
Date: Fri, 22 Apr 2011 19:44:27 -0400	[thread overview]
Message-ID: <4DB212DB.6000700@iplink.net> (raw)

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. :)

-- 
Madison Kelly - Interlink sysadmin and tech support
Office: 416-585-9971 x609
Cell:   647-501-5200 (emergencies)
Skype:  interlink.support
IRC:    digimer (freenode.net)

             reply	other threads:[~2011-04-22 23:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-22 23:44 Madison Kelly [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-22 23:44 Patches to enable MTUs >1500 in el5.6 ready for testing Digimer
2011-04-23  1:40 ` yue
2011-04-23  2:31   ` Patches " 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=4DB212DB.6000700@iplink.net \
    --to=mkelly@iplink.net \
    --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 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.