From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 8B2313FFFAD; Fri, 24 Jul 2026 21:30:03 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784928606; cv=none; b=F3KFwdAwP4fu005cSFXq5nC1UyGIdWOLOzha4mzkWmTMs+/kRAdhO6hPnnzk5J6XNZt1VBObgybDR9xRxzOHEx8NZprdVC6HkZJ3rNRoaWC4IG59eT4UvvhZ3tABAUldION+MnFWvmRdvdb9sLNGHimN3dA2lKBiMQCWC6Bv/oA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784928606; c=relaxed/simple; bh=5An+9WSGx2619TSNR0iJwvJkerAuMx6A5cmJtW0LU6w=; h=Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References: MIME-Version:Content-Type; b=UOOeTltNZNyD4HuoRfkvOrvzXalkO6GEnHGoNvpLsaLSPwvvt9hLjmoKjACXnVSmU61kYeAMJ6geRi5XbhBiePotorCNM7lg52lMK+bnXUnX2FZB8f3tbfp1fpltDhH5i5hKodwnFFk3c6jUQsdurjon+r3N/SmY7ZERyASXc0U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=dcY1My5Y; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="dcY1My5Y" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 28DAC1F000E9; Fri, 24 Jul 2026 21:30:02 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1784928603; bh=gbVBUykhRTMTCv/pcLItA/njGTwSduEcLdsDQAdKLvE=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=dcY1My5YAnKm9lrlAe9AkBnVNoKTg+LjQZSFSEtrrsbIe4ISCe95lqbKsVi0zkprl DEOAZHkRY08fpYrwLG/fGpqxrYkWqi59hKgjRCr6GLz+rGfd0sgEz/Lm1hZrbOnbvo j3Dq3EbM3CzJlaxn0jsudSRt6k5xqfjTKkfY+LlUEFJjYoEDfVAy8Mj+yFUrGH97hb CHwYcsZPSzAQrgS3h5AnFv1TwdgmQOmqr8o242dVsq+coOLwEN4d6eYQTAwSX4s3Xa GHz251yV3RIrCjHustUJC9T2M+3sYThMBKMWbahBT0EKU82w1FbIDOcGLcRjb7vLtv DxGSY+0ClTaLA== Date: Fri, 24 Jul 2026 14:30:01 -0700 From: Jakub Kicinski To: Bobby Eshleman Cc: Donald Hunter , "David S. Miller" , Eric Dumazet , Paolo Abeni , Simon Horman , Andrew Lunn , Gerd Hoffmann , Vivek Kasireddy , Sumit Semwal , Christian =?UTF-8?B?S8O2bmln?= , Shuah Khan , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-media@vger.kernel.org, linaro-mm-sig@lists.linaro.org, linux-kselftest@vger.kernel.org, sdf@fomichev.me, razor@blackwall.org, daniel@iogearbox.net, almasrymina@google.com, matttbe@kernel.org, skhawaja@google.com, dw@davidwei.uk, Joe Damato , Bobby Eshleman Subject: Re: [PATCH net-next v5 3/3] selftests/net: devmem.py: add check_rx_large_niov Message-ID: <20260724143001.5afa8631@kernel.org> In-Reply-To: References: <20260708-tcpdm-large-niovs-v5-0-34bf6fac941b@meta.com> <20260708-tcpdm-large-niovs-v5-3-34bf6fac941b@meta.com> <20260721110903.34840531@kernel.org> Precedence: bulk X-Mailing-List: linux-kselftest@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Fri, 24 Jul 2026 14:04:24 -0700 Bobby Eshleman wrote: > On Tue, Jul 21, 2026 at 11:09:03AM -0700, Jakub Kicinski wrote: > > On Wed, 08 Jul 2026 15:55:06 -0700 Bobby Eshleman wrote: > > > +@ksft_disruptive > > > +def check_rx_large_niov(cfg) -> None: > > > + """Run the devmem RX test with rx-buf-size = 16 KiB.""" > > > + run_rx_large_niov(cfg) > > > > Any idea why the devmem tests sprinkle disruptive everywhere? > > Disruptive means we take the link down, I don't think this test > > does that. > > Talked to Stan and he mentioned the original idea was not necessarily > just for link down, but any test that could be considered disruptive to > other tests, with the idea to eventually introduce some scheduling > (postpone disruptive until the end). Perhaps have such conversations on the list? IDK what Stan has in mind. > If we can get common agreement on its meaning, maybe I could submit > something into the documentation and update where its misused? > > I'll drop it from this patch since it doesn't bring down the link (and > seemingly no worries about check_rx_hds() tests not having it).