From owner-freebsd-xen@FreeBSD.ORG  Wed Jan 26 09:25:32 2011
Return-Path: <owner-freebsd-xen@FreeBSD.ORG>
Delivered-To: freebsd-xen@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id F09C0106566C
	for <freebsd-xen@freebsd.org>; Wed, 26 Jan 2011 09:25:32 +0000 (UTC)
	(envelope-from snabb@epipe.com)
Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2])
	by mx1.freebsd.org (Postfix) with ESMTP id ABD3B8FC14
	for <freebsd-xen@freebsd.org>; Wed, 26 Jan 2011 09:25:32 +0000 (UTC)
Received: from tiktik.epipe.com (tiktik.epipe.com [IPv6:2001:1828:0:3::2])
	by tiktik.epipe.com (8.14.4/8.14.4) with ESMTP id p0Q9PWiB095270
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Wed, 26 Jan 2011 09:25:32 GMT (envelope-from snabb@epipe.com)
X-DKIM: Sendmail DKIM Filter v2.8.3 tiktik.epipe.com p0Q9PWiB095270
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=epipe.com; s=default;
	t=1296033932; x=1296638732;
	bh=f31KOk022mpfXcdR9wFMkQu/Cq0Kg2MG1jRLIBxhaoY=;
	h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:
	MIME-Version:Content-Type;
	b=TrebeZ/WqipzavStMvYTAhUz31jGzn/EbW7/fPSE8ELsgjz+fNscs4WC71OLUDF3L
	BkNTpFJmvfErFNrI9kPieOnG6DOiHKTsgGIZhKvMruxDZ/4BJiFvH3wp47JSQ4wZVz
	+4YPXhsYbVC0r8mM0ZbWQd1l456hNlqcGFK2K5Vw=
Date: Wed, 26 Jan 2011 09:25:32 +0000 (UTC)
From: Janne Snabb <snabb@epipe.com>
To: Alex <joovke@joovke.com>
In-Reply-To: <4D3FDEA3.1070504@joovke.com>
Message-ID: <alpine.BSF.2.00.1101260918450.20212@tiktik.epipe.com>
References: <4D3F94B0.4080704@joovke.com>
	<alpine.BSF.2.00.1101260649160.20212@tiktik.epipe.com>
	<4D3FDEA3.1070504@joovke.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.6
	(tiktik.epipe.com [IPv6:2001:1828:0:3::2]);
	Wed, 26 Jan 2011 09:25:32 +0000 (UTC)
Cc: freebsd-xen@freebsd.org
Subject: Re: Help! Network issue with freebsd + Xen
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion of the freebsd port to xen - implementation and usage
	<freebsd-xen.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
	<mailto:freebsd-xen-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-xen>
List-Post: <mailto:freebsd-xen@freebsd.org>
List-Help: <mailto:freebsd-xen-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-xen>,
	<mailto:freebsd-xen-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Jan 2011 09:25:33 -0000

On Wed, 26 Jan 2011, Alex wrote:

> 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.

Yeah, this would be bad if it is actually happening within Xen or
dom0 and not just an issue with a counter. On bare metal this
collision processing would happen within the network card.

> 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.

Done.

--
Janne Snabb / EPIPE Communications
snabb@epipe.com - http://epipe.com/