From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: [net-next] tcp: allow drivers to tweak TSQ logic Date: Sat, 11 Nov 2017 15:27:19 +0100 Message-ID: <1510410439.12037.10.camel@sipsolutions.net> References: <1510281664.2849.143.camel@edumazet-glaptop3.roam.corp.google.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: netdev , Toke =?ISO-8859-1?Q?H=F8iland-J=F8rgensen?= , Kir Kolyshkin To: Eric Dumazet , David Miller Return-path: Received: from s3.sipsolutions.net ([144.76.63.242]:46646 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750818AbdKKO1X (ORCPT ); Sat, 11 Nov 2017 09:27:23 -0500 In-Reply-To: <1510281664.2849.143.camel@edumazet-glaptop3.roam.corp.google.com> Sender: netdev-owner@vger.kernel.org List-ID: Thanks Eric! > We expect wifi drivers to set this field to smaller values (tests have > been done with values from 6 to 9) I suppose we should test each driver or so. > They would have to use following template : > > if (skb->sk && skb->sk->sk_pacing_shift != MY_PACING_SHIFT) > skb->sk->sk_pacing_shift = MY_PACING_SHIFT; Hm. I wish we wouldn't have to do this on every skb, but perhaps it doesn't matter that much. > u16 sk_gso_max_segs; > + u8 sk_pacing_shift; I guess you tried to fill a hole, but weren't we saying that it would be better in the same cacheline? Then again, perhaps both cachelines are resident anyway, haven't looked at this now. Unrelated to that, I think this is missing a documentation update since the struct has kernel-doc comments. johannes