Date: Wed, 26 Jan 2011 19:43:15 +1100 From: Alex <joovke@joovke.com> To: freebsd-xen@freebsd.org Subject: Re: Help! Network issue with freebsd + Xen Message-ID: <4D3FDEA3.1070504@joovke.com> In-Reply-To: <alpine.BSF.2.00.1101260649160.20212@tiktik.epipe.com> References: <4D3F94B0.4080704@joovke.com> <alpine.BSF.2.00.1101260649160.20212@tiktik.epipe.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Janne, I don't know whether this is an issue with the "re" driver or something else that's affecting the "re" driver (the way Xen handles network traffic). Though as far as I know, when a collision is detected, the behavior is for the sender to invoke it's backoff algorithm and to wait a set amount of time before transmitting again. if this is actually occurring then there would be performance degradation. Would you mind adding your feedback on my PR up at freebsd.org just to let the "re" maintainer know it's not just me? The PR is 154236. Would Greatly appreciate it. Thanks in advance. On 26/01/11 17:59, Janne Snabb wrote: > On Wed, 26 Jan 2011, Alex wrote: > >> I am having an issue with high network interface collisions when running >> freebsd under XEN (I am using freebsd as my OS for a VPS). > [..] >> whether they have seen the same issue or know what may be causing it. > I can confirm seeing it here also, you are not alone: > > $ netstat -i > Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll > re0 1500<Link#1> 00:16:3e:08:b4:c7 21150230 0 0 4101045 0 4019323 > [..] > > I had not noticed it before. I am not encountering any packet loss > or other networking problems. No idea about the reason. > > This is on FreeBSD 8.1-RELEASE-p2 amd64 with GENERIC kernel. > > -- > Janne Snabb / EPIPE Communications > snabb@epipe.com - http://epipe.com/ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D3FDEA3.1070504>