All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
To: Brian Wolfe <brianw@terrabox.com>
Cc: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>,
	David Becker <becker@cs.duke.edu>,
	Xen Devel Mailing List <xen-devel@lists.sourceforge.net>
Subject: Re: vif tx drops
Date: Thu, 14 Oct 2004 09:41:38 +0100	[thread overview]
Message-ID: <20041014084138.GD17812@cl.cam.ac.uk> (raw)
In-Reply-To: <20041014083051.GC17812@cl.cam.ac.uk>

On Thu, Oct 14, 2004 at 09:30:51AM +0100, Christian Limpach wrote:
> On Wed, Oct 13, 2004 at 10:07:57PM -0500, Brian Wolfe wrote:
> > I temporarilly solved this by converting the IP to hexidecimal and
> > setting the first 2 bytes of the mac to DE:AD. Unfortunately xen
> > increments the 3rd if you set the mac. We need a way to set the mac on
> > both ends of the vif device. 
> > 
> > Opinions?
> 
> Why don't you simply convert an IP address a.b.c.d into
> AA:a:00:b:c:d and let Xen do its thing on the 3rd byte?
> I even doubt that doing AA:00:a:b:c:d would be a problem
> unless you really have IP addresses a.b.c.d and a.(b^1).c.d

or actually a.b.c.d and (a^1).b.c.d...

> on the same switch...
> 
>     christian
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
> Use IT products in your business? Tell us what you think of them. Give us
> Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
> http://productguide.itmanagersjournal.com/guidepromo.tmpl
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
> 


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl

  reply	other threads:[~2004-10-14  8:41 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-12 14:01 vif tx drops David Becker
2004-10-12 14:15 ` Keir Fraser
2004-10-12 14:49   ` David Becker
2004-10-12 15:33     ` Keir Fraser
2004-10-13 14:35       ` David Becker
2004-10-13 18:24         ` David Becker
2004-10-13 19:15           ` Keir Fraser
2004-10-13 19:28             ` David Becker
2004-10-13 20:17               ` Keir Fraser
2004-10-13 20:24                 ` David Becker
2004-10-13 20:36                   ` Ian Pratt
2004-10-13 20:52                     ` Keir Fraser
2004-10-13 20:59                       ` Keir Fraser
2004-10-14  3:07                 ` Brian Wolfe
2004-10-14  8:21                   ` Keir Fraser
2004-10-14 15:19                     ` Brian Wolfe
2004-10-14 15:29                       ` Keir Fraser
2004-10-14 15:51                         ` Brian Wolfe
2004-10-14  8:30                   ` Christian Limpach
2004-10-14  8:41                     ` Christian Limpach [this message]
2004-10-15  7:10           ` Ian Pratt
2004-10-15  8:06             ` Keir Fraser
2004-10-15 13:09             ` Alvin Starr

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=20041014084138.GD17812@cl.cam.ac.uk \
    --to=christian.limpach@cl.cam.ac.uk \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=becker@cs.duke.edu \
    --cc=brianw@terrabox.com \
    --cc=xen-devel@lists.sourceforge.net \
    /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.