From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giuseppe CAVALLARO Subject: Re: [PATCH v1] net: stmmac: Free rx_skbufs before realloc Date: Thu, 26 Nov 2015 11:26:03 +0100 Message-ID: <5656DE3B.9030602@st.com> References: <1448181858-5935-1-git-send-email-zhengsq@rock-chips.com> <1448181858-5935-2-git-send-email-zhengsq@rock-chips.com> <20151124.130924.1365382562223060152.davem@davemloft.net> <5655D004.4040502@st.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, dianders-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org, linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: David Miller , Return-path: In-Reply-To: <5655D004.4040502-qxv4g6HH51o@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+glpar-linux-rockchip=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: netdev.vger.kernel.org On 11/25/2015 4:13 PM, Giuseppe CAVALLARO wrote: > Hello > > On 11/24/2015 7:09 PM, David Miller wrote: >> From: Shunqian Zheng >> Date: Sun, 22 Nov 2015 16:44:18 +0800 >> >>> From: ZhengShunQian >>> >>> The init_dma_desc_rings() may realloc the rx_skbuff[] when >>> suspend and resume. This patch free the rx_skbuff[] before >>> reallocing memory. >>> >>> Signed-off-by: ZhengShunQian >> >> This isn't really the right way to fix this. >> >> I see two reasonable approaches: >> >> 1) suspend liberates the RX ring, although this approach is less >> desirable >> >> 2) resume doesn't try to allocate already populated RX ring >> entries >> >> Freeing the whole RX ring just to allocate it again immediately >> makes no sense at all and is wasteful work. > > This is a bug in this driver version that, to be honest, we fixed with > the first approach on STi kernel. > The patch just called the dma_free_rx_skbufs(priv) in the suspend. > I can give you this patch that is tested on my side too. > But! I do think we should move on second approach. > Indeed, also on ST platforms, when we play with suspend states > the DDR although in self-refresh the data are not lost at all. > No reason to free and reallocate all in suspend/resume. > I can test that and then provide another patch to this mailing list > asap. I have just send the patch (directly for approach #2). Peppe > > Let me know. > peppe > > >