From owner-freebsd-xen@freebsd.org  Tue Jul 14 16:15:28 2015
Return-Path: <owner-freebsd-xen@freebsd.org>
Delivered-To: freebsd-xen@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23DD49A191D
 for <freebsd-xen@mailman.ysv.freebsd.org>;
 Tue, 14 Jul 2015 16:15:28 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id F108CFC
 for <freebsd-xen@freebsd.org>; Tue, 14 Jul 2015 16:15:27 +0000 (UTC)
 (envelope-from feld@FreeBSD.org)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42])
 by mailout.nyi.internal (Postfix) with ESMTP id 11A5320948
 for <freebsd-xen@freebsd.org>; Tue, 14 Jul 2015 12:15:27 -0400 (EDT)
Received: from web3 ([10.202.2.213])
 by compute2.internal (MEProxy); Tue, 14 Jul 2015 12:15:27 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=RUZPMyyhY8tx6mL
 /ZW0HILCbrcw=; b=uOgVhkdFx5kXoD7Pz66E0dA7RKrMXvzb4DIlMYUEU/Ck0BQ
 7jrmUbduemOU1nzvukEv1JLv2cWSYajnoNByN28B2GpPVdxTf73j4Cl1heRy5zrM
 1bnzlibsNa3PrbPgnwqej5cVdMQlToio9NzaZenihFEiATY70MskwSQxzjNY=
Received: by web3.nyi.internal (Postfix, from userid 99)
 id E17EC103B8D; Tue, 14 Jul 2015 12:15:26 -0400 (EDT)
Message-Id: <1436890526.3162974.323521249.6B73E6E2@webmail.messagingengine.com>
X-Sasl-Enc: memLubk/i4l3wTdDaW1JUT2YlfDBYmB0R2384ypFxvd2 1436890526
From: Mark Felder <feld@FreeBSD.org>
To: freebsd-xen@freebsd.org
Cc: gnn@freebsd.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-63a5d8c6
Subject: Re: Networking under Xen
Date: Tue, 14 Jul 2015 11:15:26 -0500
In-Reply-To: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com>
References: <4E7B7075-4E0D-4EA7-9F5D-6D252CFBD487@gmail.com>
X-BeenThere: freebsd-xen@freebsd.org
X-Mailman-Version: 2.1.20
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/options/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: Tue, 14 Jul 2015 16:15:28 -0000



On Tue, Jul 14, 2015, at 07:36, Sydney Meyer wrote:
> Hello everybody,
> 
> i have noticed some odd behaviour with networking under Xen with FreeBSD
> 10 as a DomU.
> 
> - IPv6 (TCP) bandwith drops from ~10 Gbit/s IPv4 to around 3 Gbit/s IPv6.
> (measured with iperf)
> 

What is the "before" and "after" here? When is FreeBSD successfully
doing 10Gbit/s and when isn't it? Is pf enabled? Are you scrubbing?

> - Dropped/Stalled Connections with TCP Segmentation Offload and pf
> enabled.
> 

TSO is a known issue. I've been turning it off for years to get FreeBSD
to play nice on Xen.

> - IPSEC-enabled Kernel TCP Performance drops from ~10 Gbit/s to ~200
> Mbit/s (iperf).
> 

Are you saying FreeBSD non-IPSEC kernel can do 10Gbit/s TCP performance,
but IPSEC kernel immediately drops it to 200Mbit/s?