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 5ED95CD5BC9 for ; Thu, 5 Sep 2024 14:32:08 +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:Content-Transfer-Encoding: Content-Type:In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=FsQk6z3HEBxGfR6MpE4YothAxzaD5ug0Mh6OH+yVUjs=; b=n6DODU4e6JaX0/i4xePBE/jxmc pKvLKs5wU6hFDgB+8BsmILOkTOqC6+d2QCNJhiH2KH2Nmi7YKLLgfr4FCRukVPjOM+FaNr19hmweb x1zT7Cg6HzN3sxUKmycoxdQsDSjG61daWoHFE3T+ace3BoRwogYYciU61zNyxk+cAUQn+qhLtl8pQ ILNRIggFRJspt5CfK9o+KrdgfOnj68W3VhVQFFVwHKE9oa2hOSmQWDE8k/ZFcMjjLvbFQ/iofUgzJ 1sfVo4xHZOl0BRzLYUl3mzxdbG5BpSMB3cRrsWt3evuXrUIVWJMESjCQFH56EN7zi3TeUKlYMc6tF +dp9xdVw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1smDWe-00000008ivx-2SrH; Thu, 05 Sep 2024 14:31:56 +0000 Received: from out-173.mta0.migadu.com ([91.218.175.173]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1smDS2-00000008i2Q-12Sb for linux-arm-kernel@lists.infradead.org; Thu, 05 Sep 2024 14:27:11 +0000 Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1725546427; 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=FsQk6z3HEBxGfR6MpE4YothAxzaD5ug0Mh6OH+yVUjs=; b=RUUKKGQnv8uB849iNLPKm92xmx+iHZQGUdonlJPhlHsrZGhB88iEGJxyTUgD4ep038lnYY GpCnrHfPYjGvgA3LyGULP0yZHo7emvAjajdrgD7emlR8G9RorkEE+XgXcIiEa5vLwRQ+fd z8ml8I3DYTkosQCLArX5FmQmft9p4oQ= Date: Thu, 5 Sep 2024 10:27:00 -0400 MIME-Version: 1.0 Subject: Re: [PATCH net-next 0/2] net: xilinx: axienet: Enable adaptive IRQ coalescing with DIM To: Simon Horman 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 References: <20240903192524.4158713-1-sean.anderson@linux.dev> <20240904163503.GA1722938@kernel.org> Content-Language: en-US X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Sean Anderson In-Reply-To: <20240904163503.GA1722938@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240905_072710_472764_9B952602 X-CRM114-Status: GOOD ( 15.37 ) 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 9/4/24 12:35, Simon Horman wrote: > 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. > Well, I would normally do so, but that patch is a fix and this series is an improvement. So that one goes into net and this one goes into net-next. I've been advised in the past to split up independent patches so they can be reviewed/applied individually. --Sean