Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3062382imu; Mon, 17 Dec 2018 12:35:44 -0800 (PST) X-Google-Smtp-Source: AFSGD/UDirR6BJTu1shOz/w7LE3SHP0qyPlz1N4hkrnV2Jnel+jk+AMOu+kcj0r0uAubjRSr/7YU X-Received: by 2002:a17:902:d911:: with SMTP id c17mr14360708plz.151.1545078944716; Mon, 17 Dec 2018 12:35:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545078944; cv=none; d=google.com; s=arc-20160816; b=YedUPEcQ/ZQ6x37GFCLopDfqkA+LjkRhTc9ZOzIRQ1Ae5FIiTkYp/gPfDhzGCVzAsF 1Iw8HjSccfnlYeerVlcLnbnOcX603lhfkG+NBzUEupPJJhUHVQNlWugbFR4oSSUw5qRq rGWcfmYgvwA3qaijzMHvTuc+VC0PbRt15a4159r7ZN6Qzr/GmzB/BRSAI2dNKH3pREeV be9lxUuSOXp3Hj0TvX44aDTI7jwZgG9L6GIR22ZcrDAUAfOLWtauQvUGUhMAhHyFTQLs DysIIdMmTnOGR2nf1XjVscXNNklG4QEU9HEiEoIJy9MvgURkhtkZQYWmUqCa3xkkd6En SsnA== 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 :references:in-reply-to:from:subject:cc:to:message-id:date; bh=29swdbXZNF4KGJbapVZQpufOL5bf2mF5VeJSPwB4ipU=; b=cyohBqNirHoz/aRgttiewm4zrYd00qJkDl0/2YEX/DtUihwjekRtRDkSf6A3JFYwum GB3E9qjqyBXgTURerSN0w/dPFQ2Krj0lHoHjg+wlf9KTZSQnsPFJJEPd9j4NOqZsd6D3 Nrw4nx8oc7ogDXywQnzf9Un1UcSjd8s/4nAIl/L+GYL8oVfHGwSLnml+gJ/iuSr2kI+U Ffo2FDW6zcwq3lNvcqxuelL0Kr2bJHPWB/nu9BFWE2yKvz4Xqvw3SFzqnpBL9pekGicf SC9X+PkIYRf2RQ4IKoeUDRuHn6sYsIcIyqgNYTnjsXf4w4WKTimgqOZ5S7yhepNattup fsRw== ARC-Authentication-Results: i=1; mx.google.com; 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 u4si4412678pga.91.2018.12.17.12.35.29; Mon, 17 Dec 2018 12:35:44 -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; 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 S2387767AbeLQTNE (ORCPT + 99 others); Mon, 17 Dec 2018 14:13:04 -0500 Received: from shards.monkeyblade.net ([23.128.96.9]:42076 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1732996AbeLQTNE (ORCPT ); Mon, 17 Dec 2018 14:13:04 -0500 Received: from localhost (unknown [IPv6:2601:601:9f80:35cd::cf9]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id 8039310199D44; Mon, 17 Dec 2018 11:13:03 -0800 (PST) Date: Mon, 17 Dec 2018 11:13:02 -0800 (PST) Message-Id: <20181217.111302.105056511088497169.davem@davemloft.net> To: xuechaojing@huawei.com Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, wulike1@huawei.com, chiqijun@huawei.com, fy.wang@huawei.com, tony.qu@huawei.com, luoshaokai@huawei.com, nhorman@redhat.com Subject: Re: [PATCH 1/1] net-next/hinic:optmize rx refill buffer mechanism From: David Miller In-Reply-To: <20181216223234.24031-1-xuechaojing@huawei.com> References: <20181216223234.24031-1-xuechaojing@huawei.com> X-Mailer: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Mon, 17 Dec 2018 11:13:03 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Xue Chaojing Date: Sun, 16 Dec 2018 22:32:34 +0000 > In rx_alloc_pkts(), there is no need to schedule a different tasklet for > refill and it will cause some extra overhead. this patch remove it. > > Suggested-by: Neil Horman > Signed-off-by: Xue Chaojing In future submissions please formation your Subject line properly. First, there should always be a space character after the ":" following the subsystem prefix. Next, "net-next" belongs inside of the '[]' so "[PATCH net-next N/M] ". However, when you have a single patch, there is no reason to give the "N/M" part, so you can just drop it in this situation. Please also capitalize the text after the subsystem prefix string. Therefore this Subject must be formatted exactly like this: Subject: "[PATCH net-next] hinic: Optimize RX refill buffer mechanism" But meanwhile you must address the feedback given to you by Neil and myself. You absolutely MUST NOT receive a RX packet if you cannot successfully allocate a replacement buffer for the RX ring in that slot. It allows the RX ring to become empty, which many cards respond to by hanging. It would really serve you poorly if you continue to ignore our feedback because addressing it is a requirement before we will be able to consider integrating your work. Thank you.