From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-171.mta0.migadu.com (out-171.mta0.migadu.com [91.218.175.171]) (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 89B7B1B4133 for ; Tue, 18 Feb 2025 16:18:18 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.171 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1739895500; cv=none; b=JTzjyqas21TDyl7I5vg+cnfRR9slq0+eFMBtKnRKSszJ5zlPA4I7OMMLfCBHPHnHsH7rbcds0Zq9ylUJ2yxvyAcTunxC9YEWiMtIakEBZCJMk6o68cMljUoM0284Q8S7RakXWIXeQ6jb9N5Cbm/zr7g3r1GcFQ2FmEleMvPmivY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1739895500; c=relaxed/simple; bh=Z7xCo6Os7CElV3/n1hsqRxtfI6J2UdkQe0H9AW2yIH4=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=g3I+oSRzn3nMVPv6wzbkjN+tF1OWiFA+eBUiFhT/gfUJMv57Zzm1dyLzKzaftR5sriQWWy0oNMP5MiLoUGb7QLcWKTXxgPUFg2/JF0uq6Bi9yYo1cTHd/btdiz90RGvxTA+3h2aEkpnX70B5klsgDajgoTHEHr4+GpL45WO2ZTQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=E/1xu/wM; arc=none smtp.client-ip=91.218.175.171 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="E/1xu/wM" Message-ID: <7446c987-3286-4b8a-a105-96443275d4d4@linux.dev> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1739895496; 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=gwx1IfTKh1rDEZJZPwub8nyeYTYzilJEqxSN8ou+0bA=; b=E/1xu/wM2vYeLhBelvWB1ep+Erfy5NmqLoD18c34a+RTGqEMMLuJWDWww4FNlWeRqTnMvU FBrQAhQ35VNhqWo0A23fqx9r3saaVlbNJW68Y2I2ltIg0PFt4FQd1IhHYebD1qpHbXo9FX I/qF3/bQpYDcElBYNYFJpRqvhtYWFmc= Date: Tue, 18 Feb 2025 11:18:12 -0500 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH net-next] net: xilinx: axienet: Implement BQL To: Andrew Lunn Cc: "Gupta, Suraj" , "Pandey, Radhey Shyam" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Paolo Abeni , "David S . Miller" , Jakub Kicinski , "Simek, Michal" , "linux-arm-kernel@lists.infradead.org" , Eric Dumazet , Andrew Lunn References: <20250214211252.2615573-1-sean.anderson@linux.dev> 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: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT On 2/18/25 11:16, Andrew Lunn wrote: >> > Could you please check if BQL can be implemented for DMAengine flow? >> >> I can have a look, but TBH I do not test the dma engine configuration since it is >> so much slower. > > It might actually benefit more from BQL if it is slower? Actually, it will benefit less. The hardware is the same, so the slowdown is entirely due to extra CPU overhead. From the CPU's perspective, the queues actually drain faster than normal. --Sean