Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp1383024ima; Fri, 1 Feb 2019 23:05:58 -0800 (PST) X-Google-Smtp-Source: ALg8bN4PhS9PSpd0srJ30dyhPoSzJkSHdUCLfP2YM4yXS+BndmbKe/ChmFpVjA9fFTTorJNty/eW X-Received: by 2002:a63:d604:: with SMTP id q4mr38228285pgg.175.1549091158024; Fri, 01 Feb 2019 23:05:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1549091157; cv=none; d=google.com; s=arc-20160816; b=h5/E+ZWKmXbExNjE2bej6tkeS5HKm6r2czBPIOu5RVuPAjcb2lj12nAJKYXSjy9o8k dGpURM2fzD3X6TAmvryDpxZ/y1r0mSup+hCdPByPKVDKpZCKtNcq1zkoRE6yS/egav3w 6gh5qVosLXINS7k2oPnJHYXN+BI9MIyT/P4x64PV/pQ1VPplSZdh7K6l33ggoY/qh7US nP6h+3MR11f3D/qQWkCoaUQ9+oYvjFB8AD8QM338lR4tvwZiPOdKEwGxa8qocLfmcYXD TsCPjHhB1LW6XwWo0eZ3sCATu6lJzbFYdu1Y3HqY/uHSbXxz/pJAj8F7AHFzqMDD4/HQ 5lug== 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 :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=VqtZCAM8aMEkU1Vxv8nZ/3avC5flqPGIuAVx2UccIVs=; b=gHMq+lRy1g+/OyiOLO6fnkOV7i/qjmkSHs81dffP0VOXJ561cSBn7wS0tA1AQMbo1D 3bz6C8NJoTRXZKr67T7PCdF76m4cnN3ntwMP/fKC+847Tmu1KWapAooF4uxaJJnpA+T8 AdYjYmCNboU1d1NDMb97ZPdOYkQJ6trM/7MWGDJVxDUTEV4I9s8fRNSxdV0iCKVbAigr aarmSrCTRLD9EKBLSdfG9A1by2pR208pNyhOdkA7kMXmw7nc1XdrugtuCLFRU433pw6V t6VbRf8cO7jth7jBHjFrRY9T3a9t4PhRbHzJFvBiSp3SpnMWXKMm5YbSn0SMRypJuwOv 8AMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=KWBInFJ9; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id x64si9414720pfx.87.2019.02.01.23.05.08; Fri, 01 Feb 2019 23:05:57 -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=@messagingengine.com header.s=fm1 header.b=KWBInFJ9; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727539AbfBBGrN (ORCPT + 99 others); Sat, 2 Feb 2019 01:47:13 -0500 Received: from out1-smtp.messagingengine.com ([66.111.4.25]:53631 "EHLO out1-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727154AbfBBGrN (ORCPT ); Sat, 2 Feb 2019 01:47:13 -0500 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 3AD2921F0C; Sat, 2 Feb 2019 01:47:12 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 02 Feb 2019 01:47:12 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=VqtZCAM8aMEkU1Vxv8nZ/3avC5flqPGIuAVx2UccI Vs=; b=KWBInFJ9cP8LxdZoWAsVpQlQsnijmQXHeAAxS6i9jMbgd7gr1tfNmQD9C BX9GJ9EQQWIQ6RcHNO/h4HxbuDt1oqkHnod5YLzg+x6XjX1kyB4HiMqFiPz6fvPi hbF7FB/Rax9TJw64b5tjeaooXasMJyxvpyOg2yjhoHHkRss2xs9RBibMTO/dxM1t JT14vc+TDXdbRorDw8VOAf8Kzd5me7cZhRzjBZD55duDLQQtTFd9THk9N81ScF6e tUIzdOxIVHPSIh63Zb2wgWRXGYACC+qXiV+GkOqtaivHleb0e4+Y3+UA/Vnv26Us Dp7ZS1lJPTag2oqeDRCNpxz1yI9JA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrjeelgdellecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhepuffvfhfhkffffg ggjggtgfesthejredttdefjeenucfhrhhomheprfgvkhhkrgcugfhnsggvrhhguceophgv nhgsvghrghesihhkihdrfhhiqeenucffohhmrghinhepshhouhhrtggvfhhorhhgvgdrnh gvthenucfkphepkeelrddvjedrfeefrddujeefnecurfgrrhgrmhepmhgrihhlfhhrohhm pehpvghnsggvrhhgsehikhhirdhfihenucevlhhushhtvghrufhiiigvpedt X-ME-Proxy: Received: from Pekka-MacBook.local (89-27-33-173.bb.dnainternet.fi [89.27.33.173]) by mail.messagingengine.com (Postfix) with ESMTPA id C55F1E4078; Sat, 2 Feb 2019 01:47:07 -0500 (EST) Subject: Re: [PATCH] mm/slab: Increase width of first /proc/slabinfo column To: Christopher Lameter , "Tobin C. Harding" Cc: Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <20190201004242.7659-1-tobin@kernel.org> <01000168a6e8944d-b8e72739-2611-4649-a8d2-304b98529b7d-000000@email.amazonses.com> From: Pekka Enberg Message-ID: Date: Sat, 2 Feb 2019 08:47:03 +0200 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:60.0) Gecko/20100101 Thunderbird/60.5.0 MIME-Version: 1.0 In-Reply-To: <01000168a6e8944d-b8e72739-2611-4649-a8d2-304b98529b7d-000000@email.amazonses.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 01/02/2019 4.34, Christopher Lameter wrote: > On Fri, 1 Feb 2019, Tobin C. Harding wrote: > >> Currently when displaying /proc/slabinfo if any cache names are too long >> then the output columns are not aligned. We could do something fancy to >> get the maximum length of any cache name in the system or we could just >> increase the hardcoded width. Currently it is 17 characters. Monitors >> are wide these days so lets just increase it to 30 characters. > > Hmm.. I wonder if there are any tools that depend on the field width here? > It's possible, but it's more likely that userspace parses by whitespace because it's easier to write it that way. At least procps, which is used by slabtop, is prepared to parse a cache name of 128 characters. See the scanf() call in parse_slabinfo20() function in proc/slab.c of procps: http://procps.sourceforge.net/ Of course, testing with slabtop would make sense. - Pekka