From nobody Thu Oct 26 18:28:57 2023 X-Original-To: freebsd-current@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 4SGZ7p5SZPz4y7h3 for ; Thu, 26 Oct 2023 18:29:10 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 4SGZ7p3b2Fz3FKW for ; Thu, 26 Oct 2023 18:29:10 +0000 (UTC) (envelope-from rick.macklem@gmail.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x62e.google.com with SMTP id d9443c01a7336-1cac80292aeso9764445ad.1 for ; Thu, 26 Oct 2023 11:29:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698344949; x=1698949749; darn=freebsd.org; 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=e77caBTcZP+qjpatpBJHu26qKv7Q306QZzbr9QY51G8=; b=ODum1vYg5TOmgzUL9UcRWwyLeoN2gwFRd1jC25ARhO26gQHEifXKwOsXBmq+K8W2xF WZs7KkvNBA5+JvkKqpxk4z53GYJr11Sm4jB/gfzCCy+fxhikUQw2zDB7A37vqtQmcMFQ /eoWugBLILPNTmJiE37TCO+iP/Zw6o4RYbmKsha39bZ04jbO2BmDXQLBgGVdqaMCnnta acENBzgciyMwa42bEe4Wo5YbJL1vvKzTvGkDfLZGIZ/EAYSZyaxjfnTQPSD3F31eB/Oh /Pg2D7tgkZfsvBETBjfdBnFRCUJ57/UxqqloFDFZoWmZl8HCDS1LfGnFxn/05g9sj64y cCtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698344949; x=1698949749; 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=e77caBTcZP+qjpatpBJHu26qKv7Q306QZzbr9QY51G8=; b=RK8c9aoFkBCNull5o0qYx3dvXEkQmkPKLZ2dOp9Hfdt7buWZmpC/Gzr1QfRWwRg+li rQ0Dg89yHCi0mTCVsuNsaxc+iGbLkhWiVb3BkAFRwVfHdCeBbYt7fNuptbFGpBXmjBbh +6na1lhZdK6a4chBMmWO/3AB5RC4pIEzJgHP5VRdE9zDizDibctu4hsPAbRXCBjd42DC 5HuSItIsA15uRhHd2rBlvqazAQO6XoqdmfFiFqlbwr2xNGnWfBvE5yGc2vqMtI/2yfQ5 JeS/oK9CZNiqRaCayuCXL/PJD0wRCsMIg86ut3FHFCSgkG0/A06MRHG/H6ULYi8IXV7s p3rQ== X-Gm-Message-State: AOJu0Yyw+50PnBgNjjuZVWxHrfn7EQPx9y2KexY5isiFmR0g7owL1rZs GGl9pFeLo0Z/qUlVPWuubsmq4KlRrz+odHC4Ew== X-Google-Smtp-Source: AGHT+IErlAGc6R9yg9M1MvNRkvFHG3Pnf783pfSbPY8w9wP+rpKf2j8UQ0j4pNxsdrHExdKVWoBSgPfY865r90afAhE= X-Received: by 2002:a17:903:11c4:b0:1c3:3363:8aea with SMTP id q4-20020a17090311c400b001c333638aeamr361551plh.61.1698344948907; Thu, 26 Oct 2023 11:29:08 -0700 (PDT) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 References: <63874.1698283976@kaos.jnpr.net> <48556.1698289785@kaos.jnpr.net> In-Reply-To: <48556.1698289785@kaos.jnpr.net> From: Rick Macklem Date: Thu, 26 Oct 2023 11:28:57 -0700 Message-ID: Subject: Re: RFC: NFS over TLS stats To: "Simon J. Gerraty" Cc: Freddie Cash , FreeBSD CURRENT Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; TAGGED_FROM(0.00)[] X-Rspamd-Queue-Id: 4SGZ7p3b2Fz3FKW On Wed, Oct 25, 2023 at 8:10=E2=80=AFPM Simon J. Gerraty = wrote: > > Rick Macklem wrote: > > > kern.rpctls.tls.snd_msgbytes: 20828 > > > kern.rpctls.tls.snd_msgcnt: 57 > > > kern.rpctls.tls.rcv_tmsgbytes: 12336 > > > kern.rpctls.tls.rcv_msgcnt: 57 > > > > > > which allows for sysctl kern.rpctls.tls > > Not sure what you mean? > > If for some reason I only care about tls I can do > > sysctl kern.rpctls.tls > > and get > > kern.rpctls.tls.snd_msgbytes: 20828 > kern.rpctls.tls.snd_msgcnt: 57 > kern.rpctls.tls.rcv_tmsgbytes: 12336 > kern.rpctls.tls.rcv_msgcnt: 57 > > otherwise I'd have to do > > sysctl kern.rpctls | grep tls > > > I am listing counts for TLS and non-TLS so they can > > be compared. As such, a "tls" in the last component of > > the name is needed, unless I list the non-TLS ones > > Ok > > > under something else like: > > kern.rpc.snd_msgbytes > > > > I currently actually have them all as: > > kern.rpc.tls.XXX instead of kern.rpctls.XXX, > > Haha I didn't notice the tls in rpctls ;-) > > > since there was already kern.rpc.gss.XXX. > > kern.rpc.tls.XXX sounds fine Ok, how does this look? kern.rpc.nontls.tx_msgcnt: 58 kern.rpc.nontls.tx_msgbytes: 20828 kern.rpc.nontls.rx_msgcnt: 58 kern.rpc.nontls.rx_msgbytes: 12072 kern.rpc.tls.tx_msgcnt: 62639 kern.rpc.tls.tx_msgbytes: 30800352 kern.rpc.tls.rx_msgcnt: 62639 kern.rpc.tls.rx_msgbytes: 13473756 kern.rpc.tls.handshake_success: 1 kern.rpc.tls.handshake_failed: 0 kern.rpc.tls.alerts: 1 It doesn't put the nonTLS and TLS lines for a given stat next to each other= , but does allow either the nonTLS or TLS stats to be displayed easily and keeps the two sets adjacent, so they can be compared easily. rick > > > > > rick