Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp2366681imu; Thu, 24 Jan 2019 11:29:52 -0800 (PST) X-Google-Smtp-Source: ALg8bN41kfYoH7NJoQOKhPp/yfMDX05Te9TXYryq9zOxpk/AqmzsD+/jJVvrY2K7pQdrnOMNisdO X-Received: by 2002:a62:db41:: with SMTP id f62mr7951668pfg.123.1548358192001; Thu, 24 Jan 2019 11:29:52 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548358191; cv=none; d=google.com; s=arc-20160816; b=rfbt2ABxBGI/Ekr2945D/h6kOkYkhGAnofjOUQF7uphzUreekWQigaiSgQrRGFd6w/ c/ufOcdcbG95vp7Yssu2cf63XUwCVaOmd04vdOsdLnSVn/1G/k4i6lMXtknhYoL6xa3S Rt59GdyuEjlNqoRMuJS42raGkBVw5yEqmRienCDefaMdLe6ZLEomyJO4r7f/gR/FuGC8 2n16OPr0VZRYM3pTTSW6v7wvifGRTekas1c28G/S9s+h+itJL0Q1K715GWcVh90ESJo2 teZYSa4E3VHSXuFEzwbB7W9QUETj3G0/R+5zSaJKqjKsvrjNxSktkVcFnayLDss5+bht SRXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=fO+1KWI2nRYyaYpkZjOmhbIGbmCqRrSTnRZMuoMO0gU=; b=ABTgnHE5RrkC8kaAohdQevXw4nBtcKMsxkwUPijIfMHnNY5qUtgdWnjpldNW/b6Imf 2l6ghB4jttZXFKkEukkcOPqk+unHXro1F28zzNYs06SJUBqLVmDfpYpgfp+gdQG7iqwr nyrWP7dY/VJXT99+o56F/heXXVnslSXYCimXwB489oAjzgBRliG6Mdn3ku9FzbgEHvkS e56cl50BZN0IQfPcIQi80LzY1owSWbZ5UluWegXM/0kqr9C+3M2Jyjp6hGndxNm55eki mLGNldIgciVzLYsZI4jmRLO+9RGqvAJdNyewaUjtVjLB7nXnGKbtEQZVEr19AVN6yw9v B+Eg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=UuLqSDOV; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t3si22580558plo.69.2019.01.24.11.29.36; Thu, 24 Jan 2019 11:29:51 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=UuLqSDOV; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730557AbfAXT2h (ORCPT + 99 others); Thu, 24 Jan 2019 14:28:37 -0500 Received: from mail.kernel.org ([198.145.29.99]:55360 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730379AbfAXT2f (ORCPT ); Thu, 24 Jan 2019 14:28:35 -0500 Received: from localhost (5356596B.cm-6-7b.dynamic.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 727B3218A6; Thu, 24 Jan 2019 19:28:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1548358114; bh=PS2fBftkJI0/VZcvshlPgLZoKY8UgCeWZnDyWvKEx30=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=UuLqSDOV8BxruUWr5ZnYQtj1lrnV73E1fQtGvCB/AnQkDPp7vwue84u72j7Xcfu5L 8yG1cgWF2cPqKl7A7uAidAdSWh+bEs5xmNecUVNogk2N1W88J12bxTVekrIw+82WlO 51ibPKXh+s+YD5iGhKhIOPzPQnf31jncACbQOAvU= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, "David S. Miller" , Mao Wenan Subject: [PATCH 4.4 103/104] net: speed up skb_rbtree_purge() Date: Thu, 24 Jan 2019 20:20:32 +0100 Message-Id: <20190124190205.798431289@linuxfoundation.org> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20190124190154.968308875@linuxfoundation.org> References: <20190124190154.968308875@linuxfoundation.org> User-Agent: quilt/0.65 X-stable: review X-Patchwork-Hint: ignore MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 4.4-stable review patch. If anyone has any objections, please let me know. ------------------ From: Eric Dumazet commit 7c90584c66cc4b033a3b684b0e0950f79e7b7166 upstream. As measured in my prior patch ("sch_netem: faster rb tree removal"), rbtree_postorder_for_each_entry_safe() is nice looking but much slower than using rb_next() directly, except when tree is small enough to fit in CPU caches (then the cost is the same) Also note that there is not even an increase of text size : $ size net/core/skbuff.o.before net/core/skbuff.o text data bss dec hex filename 40711 1298 0 42009 a419 net/core/skbuff.o.before 40711 1298 0 42009 a419 net/core/skbuff.o From: Eric Dumazet Signed-off-by: David S. Miller Signed-off-by: Mao Wenan Signed-off-by: Greg Kroah-Hartman --- net/core/skbuff.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) --- a/net/core/skbuff.c +++ b/net/core/skbuff.c @@ -2388,12 +2388,15 @@ EXPORT_SYMBOL(skb_queue_purge); */ void skb_rbtree_purge(struct rb_root *root) { - struct sk_buff *skb, *next; + struct rb_node *p = rb_first(root); - rbtree_postorder_for_each_entry_safe(skb, next, root, rbnode) - kfree_skb(skb); + while (p) { + struct sk_buff *skb = rb_entry(p, struct sk_buff, rbnode); - *root = RB_ROOT; + p = rb_next(p); + rb_erase(&skb->rbnode, root); + kfree_skb(skb); + } } /**