From owner-freebsd-net@freebsd.org Fri Sep 18 09:53:08 2020 Return-Path: Delivered-To: freebsd-net@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F39C23DE962 for ; Fri, 18 Sep 2020 09:53:07 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: from mail-wr1-f42.google.com (mail-wr1-f42.google.com [209.85.221.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1O1" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Bt8KG6gTSz4MsV; Fri, 18 Sep 2020 09:53:06 +0000 (UTC) (envelope-from jtubnor@gmail.com) Received: by mail-wr1-f42.google.com with SMTP id x14so4950298wrl.12; Fri, 18 Sep 2020 02:53:06 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=Mb2Teg0yYbgv8NVYFwyNgPiJmfsXJhfS1QtGLa7Q2FA=; b=W4AZWITDCOuDfrOagasSvtghG/oGjDEdQ+NJrI5F6ybE66ow/DIylaerVvTHOTJyvy ZiOjNN2XmeDSpJoAvSuhU/5OxhcxTcaayUR30xXfBRtoO1UW1b/a3NKXV5X3hRX8zJGp jRnMHj7dfXvN7XgCMFRV41R4E/lx6CRcm5gPnCrLStlZV5HtxojqG5QdJla33bRQSo6M eaJhet+uJO3NQ9Si9iU2tVULYTKNFouFtM3HafWEcnjn27XCnMdLQwc+bHdAgky9OeYo X6e4dnnYGqG/05esDVMDKydDwnpuINfhGbPtgIr8v7OkG33qnfIiPFInGCf4Q1OCVERp RYOA== X-Gm-Message-State: AOAM531ZzY5mzP0oabEdrrrc5ul264aRrrj16kd6Tx0RWlwfuAGAF/42 0ZzxcGeORozgfDH0seM/jY45yqB6hn+xDMm/Ew+IkNCb X-Google-Smtp-Source: ABdhPJy5AVDxdTltY+qmRfbsGR9TDgfaetOFLUrwP9sMZAhAqZMjECdlgY6s6Qa1MkpLrcYWEEn4mTDQdn09jsehG3I= X-Received: by 2002:adf:e601:: with SMTP id p1mr39692219wrm.172.1600422785166; Fri, 18 Sep 2020 02:53:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jason Tubnor Date: Fri, 18 Sep 2020 19:52:53 +1000 Message-ID: Subject: Fwd: Fragmentation of em(4) traffic (potentially others) when using vlanhwtag 12.2-BETA1 To: vmaffione@freebsd.org, mmacy@freebsd.org, freebsd-net@freebsd.org, erj@freebsd.org X-Rspamd-Queue-Id: 4Bt8KG6gTSz4MsV X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of jtubnor@gmail.com designates 209.85.221.42 as permitted sender) smtp.mailfrom=jtubnor@gmail.com X-Spamd-Result: default: False [-1.19 / 15.00]; ARC_NA(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_TLS_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[4]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_DN_NONE(0.00)[]; DMARC_NA(0.00)[tubnor.net]; SH_EMAIL_DBL_DONT_QUERY_IPS(0.00)[0.0.0.0:email,0.0.5.200:email]; NEURAL_SPAM_SHORT(0.27)[0.274]; NEURAL_HAM_LONG(-0.55)[-0.553]; NEURAL_HAM_MEDIUM(-0.91)[-0.907]; DBL_PROHIBIT(0.00)[0.0.0.0:email,0.0.5.200:email]; RCVD_IN_DNSWL_NONE(0.00)[209.85.221.42:from]; FORGED_SENDER(0.30)[jason@tubnor.net,jtubnor@gmail.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.221.42:from]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; FROM_NEQ_ENVFROM(0.00)[jason@tubnor.net,jtubnor@gmail.com]; MAILMAN_DEST(0.00)[freebsd-net]; RCVD_COUNT_TWO(0.00)[2] Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.33 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.33 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Sep 2020 09:53:08 -0000 Cross-posting this issue that exists in the 12.2 cut. Cheers. ---------- Forwarded message --------- From: Jason Tubnor Date: Thu, 17 Sep 2020 at 10:49 Subject: Fragmentation of em(4) traffic (potentially others) when using vlanhwtag 12.2-BETA1 To: freebsd-stable Hi, Doing some edge case testing with 12.2-BETA1, I have come across fragmentation issues when vlanhwtag is enabled on the em(4) network device (device listed below), causing IPSec traffic moving through a bhyve 'router-on-a-stick' to tank on send. When you disable (-vlanhwtag), this issue goes away and full speed send is possible. Here is a snip of the traffic leaving for the internet after traversing several VLANs through a bhyve router with vlanhwtag enabled: 10:09:54.173412 Dest.443 > Source.60901: . ack 12384 win 492 (DF) 10:09:54.173936 Source.60901 > Dest.443: . 38413:39873(1460) ack 3837 win 1027 (frag 20228:1480@0+) 10:09:54.173937 Source > Dest: (frag 20228:1420@1480) pciconf -vlbc em0@pci0:0:25:0: class=0x020000 card=0x308617aa chip=0x15028086 rev=0x04 hdr=0x00 vendor = 'Intel Corporation' device = '82579LM Gigabit Network Connection (Lewisville)' class = network subclass = ethernet bar [10] = type Memory, range 32, base 0xf7d00000, size 131072, enabled bar [14] = type Memory, range 32, base 0xf7d39000, size 4096, enabled bar [18] = type I/O Port, range 32, base 0xf080, size 32, enabled cap 01[c8] = powerspec 2 supports D0 D3 current D0 cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message cap 13[e0] = PCI Advanced Features: FLR TP Happy to provide further information if required and perform testing to make sure the 12.2 release is polished. Thanks, Jason.