From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gerd Hoffmann Subject: Re: [1/3] [XEN] gnttab: Add new op unmap_and_replace Date: Wed, 06 Jun 2007 09:50:40 +0200 Message-ID: <46666750.2080600@redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: Xen Development Mailing List , "Daniel P. Berrange" , Herbert Xu List-Id: xen-devel@lists.xenproject.org Keir Fraser wrote: > On 4/6/07 15:12, "Gerd Hoffmann" wrote: > >> I'd rather name the things what they are. Name the ethernet interface >> eth0, name the bridge xenbr0 or virtbr0 or just br0. Drop peth0. The >> only reason for the renaming was to trick the distro setup scripts by >> doing "ifdown eth0; bridge-setup (with eth0 -> peth0 and veth0 -> eth0); >> ifup eth0". > > That trick still applies though, right? Just with xenbr0->eth0. The decision > to use or not use this trick seems orthogonal to whether or not we have the > veth0/vif0.0 loopback. With the loopback being gone it is _much_ easier to have the distribution network scripts setting up the bridge because the setup can look the same no matter whenever a xen kernel or a native kernel has been booted. And have the bridge setup explicitly wired up in the distro configuration is much better and cleaner than playing tricks with device naming IMHO. That way you don't confuse the distro network setup tools. Also more advanced setups involving vlan and other fancy stuff are much easier to handle then. Thats why I'd like to see all device naming tricks being dropped. cheers, Gerd