From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 12C83CD4853 for ; Wed, 4 Sep 2024 16:36:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=lgyEGHmC0W0glISM7U8QOQZ2UV+rQD/8NqEp9U3vglo=; b=3LK1qN5MFnoynOBY9LXANNdQax jKNw1OhUIZWxLWoLXpdaMwuA5b7001/2+pxkWY3il4MJestSFlonTcpeTv0FLWwxpcPIUP8yZr1Yq onbhhGnRHFXnnZiMjPVkQVfBpprJoiZVzcX+2lHjx7uMc1MZjzKNEmOy8XZMr5rVKMv5KsyTXxcNr ZJ6FeQlDvQHrBktK6tp0gIRyJEZD7U30SByYgu/r5y3ATU7eCwTdp9NKN5T8N0jPsRE/WVW9UPd+M KBTC+XUTqy7oVu4qanNU3I80fCbc6OXD471UDMIzopv6Zp9jN3Y2OHMjdvj4YY32HH2URWqeTyX24 cE8vKT3A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1slszI-00000005ICc-2Ed9; Wed, 04 Sep 2024 16:36:08 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1slsyK-00000005I22-3hsw for linux-arm-kernel@lists.infradead.org; Wed, 04 Sep 2024 16:35:10 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 35C295C47F9; Wed, 4 Sep 2024 16:35:04 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 1BE3CC4CEC2; Wed, 4 Sep 2024 16:35:04 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1725467707; bh=+XpmBufS4Qg2AxW/ellAV9Ef4sdz+dYiyI0u6X+EPRk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=oloAsxZ3IWRPBByz9255WXPOb4W/lObd1foG47n47g3Jl9dnF03D0CkBnjx1zJrlk wFVtOGFH1ejRBg1hitT0fujgsHk8u2bTCgLvk+BB//ZeTfEI2jjhsFswGSdwtokgIR 110fH1tZ1ihg2TtWj1sF7QyPSwVIAroTgcAc7yVF53R8kqXoFKVtnOLqFzOIq69vYy 5jQULZ7yURAP4hxFbnJNFnjebNJraS/t8e+0hDqJ2p5yEe7J+KU1rilkn6XhbTbcYy RCL1fy8B838hXTZsZhAhMNslqstAHcLR5qVhxKeiMZgZjTo/Id99+r58r3u2M5auOD 4fXQfvspHEg+g== Date: Wed, 4 Sep 2024 17:35:03 +0100 From: Simon Horman To: Sean Anderson Cc: "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Radhey Shyam Pandey , netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Michal Simek , Heng Qi Subject: Re: [PATCH net-next 0/2] net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM Message-ID: <20240904163503.GA1722938@kernel.org> References: <20240903192524.4158713-1-sean.anderson@linux.dev> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240903192524.4158713-1-sean.anderson@linux.dev> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240904_093509_014773_2C200AE9 X-CRM114-Status: GOOD ( 11.94 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Sep 03, 2024 at 03:25:22PM -0400, Sean Anderson wrote: > To improve performance without sacrificing latency under low load, > enable DIM. While I appreciate not having to write the library myself, I > do think there are many unusual aspects to DIM, as detailed in the last > patch. > > This series depends on [1]. > > [1] https://lore.kernel.org/netdev/20240903180059.4134461-1-sean.anderson@linux.dev/ Hi Sean, Unfortunately the CI doesn't understand dependencies, and so it is unable to apply this patchset :( I would suggest bundling patches for the same driver for net-next in a single patchset. And in any case, only having one active at any given time. -- pw-bot: cr