From: Kip Macy <kmacy@fsmware.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.sourceforge.net, ian.pratt@cl.cam.ac.uk
Subject: RE: network stability with 100Mbit
Date: Sat, 5 Mar 2005 08:30:53 -0800 (PST) [thread overview]
Message-ID: <20050305082013.R72739@demos.bsdclusters.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3479@liverpoolst.ad.cl.cam.ac.uk>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1888 bytes --]
I don't think it is a case of the ethernet card being loose as it is
happening on all of the machines. And those machines were all stable
running native linux.
Do you document your usage of routed anywhere?
Thanks.
-Kip
On Sat, 5 Mar 2005, Ian Pratt wrote:
> > On one of set the machines that I have deployed I'm having
> > problems DOM0
> > falling of the network when copying large files over NFS. On the other
> > set of machines, I've never seen this problem. The immediate
> > difference
> > that comes to mind is that one of the interfaces on the first group is
> > 100Mbit. Does 100Mbit have such severe performance issues
> > that it could
> > cause the bridge to just stop forwarding packets?
>
> There certainly shouldn't be an issue with 100Mb/s. Whenever we've seen
> this before its been because the Ethernet card has been bad and looses
> carrier.
>
> Please can you try moving over to the routed rather than bridged scripts
> and see if it still occurs. I think we're going to make routing the
> default in 3.0 anyhow.
>
> Ian
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id\x14396&opÌk
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
next prev parent reply other threads:[~2005-03-05 16:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 11:18 network stability with 100Mbit Ian Pratt
2005-03-05 16:30 ` Kip Macy [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-06 22:08 Ian Pratt
2005-03-07 5:59 ` Kip Macy
2005-03-05 18:06 Ian Pratt
2005-03-05 22:35 ` Kip Macy
2005-03-05 7:15 Kip Macy
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=20050305082013.R72739@demos.bsdclusters.com \
--to=kmacy@fsmware.com \
--cc=ian.pratt@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.