From nobody Wed Jul 26 14:14:51 2023 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4R9ws64qqwz4pjKh for ; Wed, 26 Jul 2023 14:15:06 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) (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 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4R9ws63B1Lz3GS2 for ; Wed, 26 Jul 2023 14:15:06 +0000 (UTC) (envelope-from kevin.bowling@kev009.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pg1-x530.google.com with SMTP id 41be03b00d2f7-53fa455cd94so3642523a12.2 for ; Wed, 26 Jul 2023 07:15:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kev009.com; s=google; t=1690380902; x=1690985702; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=2GzO3kg4umlft+o8mADzUauLqd5s3hsDCbugw+INc2I=; b=o+GOZeY4z47TMZ9WGFsbQN/g750lHdUl/Rl+IrnVC7/EuYeixfM16wKyCJ3nSrgfMS DI+p+4Pi+8ZvlpECGwcjwND1OR4fUAj5JIsSg7lXRxeh7IHQl7C+o603byC6GszPNQaH aHemeQ2Xiuv7DczVaEogEc64UOsYesqvr2y5g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690380902; x=1690985702; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=2GzO3kg4umlft+o8mADzUauLqd5s3hsDCbugw+INc2I=; b=P4O1aZMoyRJTd4P5vg/B/fTdWjHtP6Dli85aleAbjZvp8SzW9uKXmMLknjrCHZp42P 9VR12Gkv8lfs++v2/CLn3raBMRKLV2MFU+ZzlCB3sH8SWlNeX6pOgE/8trLAxFHfK5Rt bGcAUsr15VOvFlrlBa8q/dVEZ5FspVUXpmg/Pm4Mx1dGcxPpFWK4ZqZVTFtAe9lWSqVN Mf9ZCCP7lU1h8k7rGCq80MNcTKPKn8kwAbj/v5U9Yn7fspvXbRPDCZk1tjirPTYKVXb9 0ohCWoklxC5OAmTNw2YXxly2ooxUHySubwkG6ezSZJeGCis/Q+3VYTwZ5XoN+kPVl7ql IUFA== X-Gm-Message-State: ABy/qLaE/gh06prVeMZT/9QR/ZerQ5EXzu3eLv5fwBnARR1Tikwefg6r 5S7eOdNwT3KxbW/d4kLpJ7qEs/fEYmePSfDqKPHWAw== X-Google-Smtp-Source: APBJJlGEZwaG1H4d+1GyBr39y+fAK8g/SotsoVhpRN2jEIDpiUCgNUYx/OIxZUiQD+ntNAqAgVOA+mWiK1yoUt2st1w= X-Received: by 2002:a17:90a:cb8a:b0:256:807e:6bd with SMTP id a10-20020a17090acb8a00b00256807e06bdmr1706008pju.28.1690380902445; Wed, 26 Jul 2023 07:15:02 -0700 (PDT) List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 References: In-Reply-To: From: Kevin Bowling Date: Wed, 26 Jul 2023 07:14:51 -0700 Message-ID: Subject: Re: CFT: lem(4), em(4) e1000 Ethernet TSO testing To: Cheng Cui Cc: FreeBSD Net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4R9ws63B1Lz3GS2 X-Spamd-Bar: ---- X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated On Wed, Jul 26, 2023 at 6:43=E2=80=AFAM Cheng Cui wrote: Hi Cheng, > I didn't see your post covering 82541 or 82546 chips. Does this new em(4)= change support TSO on these chips? If yes, I would be happy to test it on = them. 82541 would be excluded, while 82546 would be a candidate to enable TSO with my patches (ifconfig em2 tso tso6) > > root@s1:~ # dmesg | grep 8254 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > em0: port 0xdcc0-0xdcff mem 0xdfae0= 000-0xdfafffff irq 64 at device 7.0 on pci6 > em1: port 0xccc0-0xccff mem 0xdf8e0= 000-0xdf8fffff irq 65 at device 8.0 on pci7 > em2: port 0xbcc0-0xbcff me= m 0xdf5e0000-0xdf5fffff irq 106 at device 4.0 on pci9 > em3: port 0xbc80-0xbcbf me= m 0xdf5c0000-0xdf5dffff irq 107 at device 4.1 on pci9 > em4: port 0xacc0-0xacff me= m 0xdf3e0000-0xdf3fffff irq 101 at device 3.0 on pci10 > em5: port 0xac80-0xacbf me= m 0xdf3c0000-0xdf3dffff irq 102 at device 3.1 on pci10 > > Best Regards, > Cheng Cui > > > On Tue, Jul 25, 2023 at 10:38=E2=80=AFPM Kevin Bowling wrote: >> >> Hi, >> >> I have been working through various bugs and have come to a point >> where TSO is working on systems I have available for testing. >> >> This results in higher throughput on resource constrained systems, and >> less CPU/power usage on unconstrained systems. >> >> As of this mail, you will need to manually apply >> https://reviews.freebsd.org/D41170 on top of main to use TSO6 on >> em(4). >> >> I plan to enable TSO by default for lem(4) and em(4) during the >> FreeBSD 14 release cycle, so I would appreciate testing to address any >> remaining issues. Below, a list of chipsets that will be exempt due >> to known issues. >> >> lem(4) exclusions: >> * <82544 (although it does seem ok to manually enable for emulations >> in qemu, virtualbox, etc) >> * 82547 >> >> em(4) exclusions.. These chips have a stability workaround for high >> throughput with rapid link-flap applied that results in the TSO engine >> not being able to run at line speed. Thus, TSO would not be enabled >> by default here: >> * Intel(R) I219-LM and I219-V >> * Intel(R) I219-LM and I219-V (2) >> * Intel(R) I219-LM and I219-V (3) >> * Intel(R) I219-LM and I219-V (4) >> * Intel(R) I219-LM and I219-V (5) >> >> Regards, >> Kevin Bowling >>