From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 3F006FC00 for ; Sat, 20 Jan 2024 14:41:49 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1705761711; cv=none; b=UXyDLNX6iujJdB+t8fZvvC7WC8wgSKt+nP2utGEANv/b3S1HHXhvNr577M+eCycwZu7ZQKtJjDmju6AsBjUqZEnvUao0QRVj8RtF2NG0btTyvWOgohbiJDZ0+9h0CHr3dDlqH3YLUgEeUpTDWzHJroSU8KC2ZqEv17yxWugXNpA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1705761711; c=relaxed/simple; bh=S6BPwrXGE2thBcbHwFqMBAxcppB+4NWQZehPC54KYU4=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=Uul44HSnMwFDEiVdTLbnFmYGzkYxIJ4SUu/T73ArNaSQwFfpI1OSf4Fg+JoHWwDwcuu+pV5Mgr6UYrxJSJ0vCRmMypmrEideXM4sAAIOgSvUF8+wgkFoBUn0/JmEcmqCmAXLObW1pQlBY6ceoqq0hQ2Qu16kRRv/QYhYiWMlFuA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=NMDJStZq; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="NMDJStZq" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1705761709; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=S6BPwrXGE2thBcbHwFqMBAxcppB+4NWQZehPC54KYU4=; b=NMDJStZqzhbz0RE4QgKkxrb9jnsjhOiKqZtjEolO/9cLNnh67mHrotCjbZBLpsQKCBeril +K8jMDp3JNuOfJOQuGbi/YpL+MJ4qsBARDeTrMIUib7qeU2Mw2NBuN4zXhRNv/y/xQ0i10 6E9cMOMeGLuE+Lm3ZdK9VPFa7ke8vZI= Received: from mail-ej1-f72.google.com (mail-ej1-f72.google.com [209.85.218.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-7-Gva_p7lfM1-03XxvlvehhQ-1; Sat, 20 Jan 2024 09:41:46 -0500 X-MC-Unique: Gva_p7lfM1-03XxvlvehhQ-1 Received: by mail-ej1-f72.google.com with SMTP id a640c23a62f3a-a2b047e8f9fso89315066b.1 for ; Sat, 20 Jan 2024 06:41:45 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705761705; x=1706366505; h=content-transfer-encoding:mime-version:message-id:date:references :in-reply-to:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=S6BPwrXGE2thBcbHwFqMBAxcppB+4NWQZehPC54KYU4=; b=HDzyA102v8POtvhm31+/Mto8N+teFwQNI5GG2+pDr4zXq7W5AqMLlYQsbcNzldq6tl CbRPEKMHVIdGUAyntWB6ZISiZD1+2gmr50fm1EFtNvu1QGb+kGN4hpPrpHkefsZXPoXM RfSc0aPMSLqAFzaXZU/KbmxE2VUn+1u5M2gI5U4gLEzXUJ8/mlHVRhC9lKRCLwEQ1rx6 ODdUTetUacUHAJxNLpCmnTg9fRIoPro/rZNhGse8i043ccotX8Yg/yOP97sPmtQNcheV fy2gCv+wIBhsVFrxi+5tx39Zg8suGAm80iWtKszrdBnAOMzkFGYdsdAFOeCZTh1m6y8O tRyQ== X-Gm-Message-State: AOJu0YzxYTkeKk/472f2qU8MBsrpwE1EvyYzAi9IqxE2LBRxemtTg9Nl WRkEgwQXOw1NDa6cdFAmRQoCZNCjhTeflfR2av3r5YR9i6yxbcLDyrXOCUJHKZdCvEYkmWIoECO gcrYpaAOFVYtKhEktkuiwUwqEgiloFQN4vPpQR6CKfIa6o3RrFw== X-Received: by 2002:a17:906:5a98:b0:a23:1163:24be with SMTP id l24-20020a1709065a9800b00a23116324bemr712753ejq.95.1705761705065; Sat, 20 Jan 2024 06:41:45 -0800 (PST) X-Google-Smtp-Source: AGHT+IHuDY3A8O2vrfwcZAM0M1PYEeHPFP2ngva2JatE0cp7cV6iv0XZ5IXfV5wLy0eR3UWBYZ1gsg== X-Received: by 2002:a17:906:5a98:b0:a23:1163:24be with SMTP id l24-20020a1709065a9800b00a23116324bemr712749ejq.95.1705761704712; Sat, 20 Jan 2024 06:41:44 -0800 (PST) Received: from alrua-x1.borgediget.toke.dk ([45.145.92.2]) by smtp.gmail.com with ESMTPSA id vh3-20020a170907d38300b00a2e7d1b6042sm5542040ejc.196.2024.01.20.06.41.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 20 Jan 2024 06:41:44 -0800 (PST) Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 827D01088FD4; Sat, 20 Jan 2024 15:41:43 +0100 (CET) From: Toke =?utf-8?Q?H=C3=B8iland-J=C3=B8rgensen?= To: Jakub Kicinski Cc: Sebastian Andrzej Siewior , Alexei Starovoitov , LKML , Network Development , "David S. Miller" , Boqun Feng , Daniel Borkmann , Eric Dumazet , Frederic Weisbecker , Ingo Molnar , Paolo Abeni , Peter Zijlstra , Thomas Gleixner , Waiman Long , Will Deacon , Alexei Starovoitov , Andrii Nakryiko , Cong Wang , Hao Luo , Jamal Hadi Salim , Jesper Dangaard Brouer , Jiri Olsa , Jiri Pirko , John Fastabend , KP Singh , Martin KaFai Lau , Ronak Doshi , Song Liu , Stanislav Fomichev , VMware PV-Drivers Reviewers , Yonghong Song , bpf Subject: Re: [PATCH net-next 15/24] net: Use nested-BH locking for XDP redirect. In-Reply-To: <20240118083730.5e0166aa@kernel.org> References: <20231215171020.687342-1-bigeasy@linutronix.de> <20231215171020.687342-16-bigeasy@linutronix.de> <87r0iw524h.fsf@toke.dk> <20240112174138.tMmUs11o@linutronix.de> <87ttnb6hme.fsf@toke.dk> <20240117180447.2512335b@kernel.org> <87bk9i6ert.fsf@toke.dk> <20240118083730.5e0166aa@kernel.org> X-Clacks-Overhead: GNU Terry Pratchett Date: Sat, 20 Jan 2024 15:41:43 +0100 Message-ID: <87o7dg3w48.fsf@toke.dk> Precedence: bulk X-Mailing-List: bpf@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Jakub Kicinski writes: > On Thu, 18 Jan 2024 12:51:18 +0100 Toke H=C3=B8iland-J=C3=B8rgensen wrote: >> I do agree that conceptually it makes a lot of sense to encapsulate the >> budget like this so drivers don't have to do all this state tracking >> themselves. It does appear that drivers are doing different things with >> the budget as it is today, though. For instance, the intel drivers seem >> to divide the budget over all the enabled RX rings(?); so I'm wondering >> if it'll be possible to unify drivers around a more opaque NAPI poll API? > > We can come up with APIs which would cater to multi-queue cases. > Bigger question is what is the sensible polling strategy for those, > just dividing the budget seems, hm, crude. Right, agreed, though I don't have a good answer for what else to do off the top of my head... -Toke