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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 73363C433F5 for ; Thu, 10 Mar 2022 14:25:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243413AbiCJO0D (ORCPT ); Thu, 10 Mar 2022 09:26:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58614 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243419AbiCJOVs (ORCPT ); Thu, 10 Mar 2022 09:21:48 -0500 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A89C1C335D for ; Thu, 10 Mar 2022 06:20:37 -0800 (PST) Received: by verein.lst.de (Postfix, from userid 2407) id 5AC9868AFE; Thu, 10 Mar 2022 15:20:34 +0100 (CET) Date: Thu, 10 Mar 2022 15:20:34 +0100 From: Christoph Hellwig To: Mingbao Sun Cc: Christoph Hellwig , Keith Busch , Jens Axboe , Sagi Grimberg , Chaitanya Kulkarni , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, tyler.sun@dell.com, ping.gan@dell.com, yanxiu.cai@dell.com, libin.zhang@dell.com, ao.sun@dell.com Subject: Re: [PATCH v2 1/2] nvmet-tcp: support specifying the congestion-control Message-ID: <20220310142034.GA1038@lst.de> References: <20220309053711.2561-1-sunmingbao@tom.com> <20220309061541.GB31316@lst.de> <20220309175203.00006ee2@tom.com> <20220310083811.GA26953@lst.de> <20220310190636.00001695@tom.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20220310190636.00001695@tom.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Mar 10, 2022 at 07:06:36PM +0800, Mingbao Sun wrote: > I feel it’s not proper to create a sysfs entry for each socket. > And for those sockets that do not have the exception of > congestion-control, it’s merely a waste of resources. > > Also, since these sockets generate and die dynamically, the info > exported via fs may even do not have the opportunity to be seen by > the user. > > Anyway, if you insist that the checking and warning here is not proper, > I can remove it. Something that can happen during normal operation is per definition no something that should be warned about.