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 X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 99392C433FF for ; Tue, 30 Jul 2019 13:36:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6C3E620578 for ; Tue, 30 Jul 2019 13:36:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=nvidia.com header.i=@nvidia.com header.b="r+lHpSgh" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731159AbfG3Ngq (ORCPT ); Tue, 30 Jul 2019 09:36:46 -0400 Received: from hqemgate14.nvidia.com ([216.228.121.143]:6857 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726358AbfG3Ngq (ORCPT ); Tue, 30 Jul 2019 09:36:46 -0400 Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqemgate14.nvidia.com (using TLS: TLSv1.2, DES-CBC3-SHA) id ; Tue, 30 Jul 2019 06:36:46 -0700 Received: from hqmail.nvidia.com ([172.20.161.6]) by hqpgpgate102.nvidia.com (PGP Universal service); Tue, 30 Jul 2019 06:36:44 -0700 X-PGP-Universal: processed; by hqpgpgate102.nvidia.com on Tue, 30 Jul 2019 06:36:44 -0700 Received: from [10.21.132.148] (10.124.1.5) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 30 Jul 2019 13:36:41 +0000 Subject: Re: [PATCH net-next 3/3] net: stmmac: Introducing support for Page Pool To: Jose Abreu , Robin Murphy , "linux-kernel@vger.kernel.org" , "netdev@vger.kernel.org" , "linux-stm32@st-md-mailman.stormreply.com" , "linux-arm-kernel@lists.infradead.org" , Catalin Marinas , Will Deacon CC: Joao Pinto , Alexandre Torgue , Maxime Ripard , Chen-Yu Tsai , Maxime Coquelin , linux-tegra , Giuseppe Cavallaro , "David S . Miller" References: <1b254bb7fc6044c5e6e2fdd9e00088d1d13a808b.1562149883.git.joabreu@synopsys.com> <7a79be5d-7ba2-c457-36d3-1ccef6572181@nvidia.com> <9e695f33-fd9f-a910-0891-2b63bd75e082@nvidia.com> <1e2ea942-28fe-15b9-f675-8d6585f9a33f@nvidia.com> <8a60361f-b914-93ef-0d80-92ae4ad8b808@nvidia.com> From: Jon Hunter Message-ID: <8cb2ac13-3009-2117-d55f-6f1126b690e4@nvidia.com> Date: Tue, 30 Jul 2019 14:36:39 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: X-Originating-IP: [10.124.1.5] X-ClientProxiedBy: HQMAIL105.nvidia.com (172.20.187.12) To HQMAIL107.nvidia.com (172.20.187.13) Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1564493806; bh=HacDlfvXZhjwdQNemg3f+1KENoSodR+AJ9DMM7MgZXM=; h=X-PGP-Universal:Subject:To:CC:References:From:Message-ID:Date: User-Agent:MIME-Version:In-Reply-To:X-Originating-IP: X-ClientProxiedBy:Content-Type:Content-Language: Content-Transfer-Encoding; b=r+lHpSghERB2qPV8QeTvnlJ26APFnGjovZYNgpVjKEfFPW/0QV4n4JbQK3wiefryU GLPeczHgcGWttDAQxC2FB822Wq0g+bPt9KH1ZtSVy4nFfe9r9cdDMl7R2vNT+2fUgn 7Km7IBTaJmkwduPNxTRHA0IPPBV2rtPpgBQT+sqC2mHlyh4ACbqGGhgsidKYr3WnVe /N82lv0Ch9DQCOgNLC28RiZBE8kLfq5PNydM0cusjxXUI73fjpZVkFbhlWlBnEPZxR bEzDZbTqyJ8j7Ypg9a7H0OFD7U0EqSwJ4Ua+oquA3dRTzT4ZdF/GL07EkOBL/1LLLX 3FPxTekGsJ8Yg== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 30/07/2019 10:39, Jose Abreu wrote: ... > I looked at netsec implementation and I noticed that we are syncing the > old buffer for device instead of the new one. netsec syncs the buffer > for device immediately after the allocation which may be what we have to > do. Maybe the attached patch can make things work for you ? Great! This one works. I have booted this several times and I am no longer seeing any issues. Thanks for figuring this out! Feel free to add my ... Tested-by: Jon Hunter Cheers Jon -- nvpublic