All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Duffy <cduffy@spamcop.net>
To: Ewan Mellor <ewan@xensource.com>
Cc: xen-devel@lists.xensource.com, Kurt Garloff <garloff@suse.de>
Subject: Re: Re: network-bridge script reworked
Date: Wed, 19 Oct 2005 11:03:31 -0500	[thread overview]
Message-ID: <43566E53.7070508@spamcop.net> (raw)
In-Reply-To: <20051019155846.GR26910@leeni.uk.xensource.com>

Ewan Mellor wrote:
> I've put in the network-bridge patch, along with Charles' changes to support
> multiple bridges.  I'm in no position to test a wide variety of
> configurations, so I would appreciate some feedback from you guys.
> 
> We currently have
> 
> pdev="p${netdev}"
> vdev="veth${vifnum}"

Since the veth* device is tied to the vif0.* device, and not to the 
physical ethernet device in the machine, the way you merged it appears 
to me to be correct. I'll try it on my test machine, though, and 
validate that it Does The Right Thing.

  reply	other threads:[~2005-10-19 16:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-19  9:35 network-bridge script reworked Kurt Garloff
2005-10-19 10:58 ` Ewan Mellor
2005-10-19 11:15 ` Charles Duffy
2005-10-19 11:58   ` Ewan Mellor
2005-10-19 12:22     ` Kurt Garloff
2005-10-20 16:56       ` David Hopwood
2005-10-20 17:10         ` Ewan Mellor
2005-10-20 17:36           ` Nivedita Singhvi
2005-10-20 17:59             ` Ewan Mellor
2005-10-19 11:59   ` Kurt Garloff
2005-10-19 13:37     ` Charles Duffy
2005-10-19 15:58       ` Ewan Mellor
2005-10-19 16:03         ` Charles Duffy [this message]
2005-10-20 10:41 ` Ewan Mellor
2005-10-20 18:22   ` Kurt Garloff
2005-10-21 13:48     ` Ewan Mellor
2005-10-21 14:44       ` Kurt Garloff
  -- strict thread matches above, loose matches on Subject: below --
2005-10-19 18:07 Ian Pratt
2005-10-21  8:18 Ian Pratt

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=43566E53.7070508@spamcop.net \
    --to=cduffy@spamcop.net \
    --cc=ewan@xensource.com \
    --cc=garloff@suse.de \
    --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.