All of lore.kernel.org
 help / color / mirror / Atom feed
From: Digimer <linux@alteeve.com>
To: Teck Choon Giam <giamteckchoon@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Trying to adapt Olaf's vif MTU patch for EL5.6's 2.6.18-238.9 kernel - patch in-line.
Date: Sun, 17 Apr 2011 11:41:41 -0400	[thread overview]
Message-ID: <4DAB0A35.2020207@alteeve.com> (raw)
In-Reply-To: <BANLkTikGwJ_DuRMa9nN6H+g336bZb+0mAg@mail.gmail.com>

Morning,

  I've been able to test this patch and it works, provided that the
following patch is applied to /etc/xen/scripts/vif-bridge:

====
--- vif-bridge.orig	2011-04-17 01:58:49.000000000 -0400
+++ vif-bridge	2011-04-17 11:20:14.000000000 -0400
@@ -56,6 +56,11 @@
 case "$command" in
     online)
 	setup_bridge_port "$vif"
+        mtu="`ip link show $bridge | awk '/mtu/ { print $5 }'`"
+        if [ -n "$mtu" ] && [ "$mtu" -gt 0 ]
+        then
+                ip link set $vif mtu $mtu || :
+        fi
 	add_to_bridge "$bridge" "$vif"
         ;;
====

  Please note, this differs slightly from Olaf's patch found here:
http://lists.xensource.com/archives/html/xen-devel/2011-02/msg00351.html

  The only difference is that, in Xen 3.0.3/EL5.6, the variable name is
'$vif', not '$dev'. I'm trying to create a proper patch for the
xen-3.0.3 but am having trouble with source rpm. I'll post back with a
proper patch once I get it working.

  This is related to bz 697021
(https://bugzilla.redhat.com/show_bug.cgi?id=697021).

-- 
Digimer
E-Mail: digimer@alteeve.com
AN!Whitepapers: http://alteeve.com
Node Assassin:  http://nodeassassin.org

  parent reply	other threads:[~2011-04-17 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-17  1:44 Trying to adapt Olaf's vif MTU patch for EL5.6's 2.6.18-238.9 kernel - patch in-line Digimer
2011-04-17  3:23 ` Teck Choon Giam
2011-04-17  3:29   ` Digimer
2011-04-17  5:57   ` Digimer
2011-04-17 15:41   ` Digimer [this message]
2011-04-17 16:51     ` Digimer
2011-04-18 16:22       ` Konrad Rzeszutek Wilk
2011-04-18 16:31         ` Digimer
2011-04-19  4:46     ` Digimer

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=4DAB0A35.2020207@alteeve.com \
    --to=linux@alteeve.com \
    --cc=giamteckchoon@gmail.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 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.