Received: by 2002:ac0:8c9a:0:0:0:0:0 with SMTP id r26csp414506ima; Thu, 31 Jan 2019 19:36:17 -0800 (PST) X-Google-Smtp-Source: AHgI3IZHsIki94/wAeuYaoyF5W3ueRWukL8R1vH4wIrvDz4qQWudF+uyGnx8JGR3pC3PX0yNDxrW X-Received: by 2002:a63:dc54:: with SMTP id f20mr655709pgj.410.1548992177897; Thu, 31 Jan 2019 19:36:17 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1548992177; cv=none; d=google.com; s=arc-20160816; b=Eo2torx4URZ4Gx7+Gq5hDl5Wt6gUk0Y+ZzVWuE6AD3D0TvxPkv42lLQfxFvmXUxuS7 l2HF3PmY3ZA88hzP8p8GqvKY9hxHIH7pmOCuRz2I9wxZGU8RN67XJxDSEbDJHvFNq0FM JMXN86+NRnHXktlJX7AsBrt7kcM3RCWyuh8RXRUqChARZpXxsXibuldLQ+UybsoXoLVt E+iVVQkAfY5/M+1CO4lbVzelLzsXoGX6aFdGXbg7WMRR5AuYqJXARBd1sIQZ3M6javOE rP9xR1oxAu9Y/WWacK/GRaOU2tIBT8Y/gJpZO8NqOo6TuCbsyoPPfedJYtKz8v8WjEQf aZWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature:dkim-signature; bh=HSl4cOeylKJWGZ1gRfcpgzkKgRGUpcow+/PQb70GWe4=; b=ALw+xJW0on+u14nUP+U358VtXrHuCnXdq8Qlqs6Mx00fGBoOpnrgWiEDuOrbSl5swg aeRa/RDZjWIG9tgycMjJ25iKC6kLSbTuEGBKKQ3l5dqD8qDpNRf4DbbSKyRE5R8kGMRU yD6izcHnDFGiJhMcEw47beQMfhZ9Zejr2mRVKKdTtLkXLvnWdAFzkcnRZZBktPj6SoMf hXg06aaqIjAaXsrRQDOKSYP/oL37Uu4JSLJuhnKe07TVkHwzDyxQhN9emz3QLhHNPzU/ LSrHU8X7APX9cLGFKG/rXeYPRJpu+eHCan269bOrAx2pLJY9m5ahzWvB7rnvJ76pZq7B Q/Xg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@tobin.cc header.s=fm2 header.b=HcVwliAM; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=j63DN7o0; 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 31si6363720plj.244.2019.01.31.19.36.02; Thu, 31 Jan 2019 19:36:17 -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=@tobin.cc header.s=fm2 header.b=HcVwliAM; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=j63DN7o0; 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 S1728529AbfBAC6X (ORCPT + 99 others); Thu, 31 Jan 2019 21:58:23 -0500 Received: from wout2-smtp.messagingengine.com ([64.147.123.25]:42785 "EHLO wout2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725831AbfBAC6W (ORCPT ); Thu, 31 Jan 2019 21:58:22 -0500 Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 524622DF3; Thu, 31 Jan 2019 21:58:21 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Thu, 31 Jan 2019 21:58:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tobin.cc; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=fm2; bh=HSl4cOeylKJWGZ1gRfcpgzkKgRG Upcow+/PQb70GWe4=; b=HcVwliAMgEFBku4Jcy/ar1EZHhhVXBxHKogoSpDlCVo jz9id7tTOaY2YqB28p3BPdb1Hzo9XDtIyARJH/kwd5ZRQp7N7moYxfPuC37Oy7lS Up5Tfs2t7KZzqtMxNr8E4n+JEQQiJ8dSkHnqWS6IK4Dypd4p8hbs9AVLwpIiBdRF Yp5c6yY1HizhocF1q7CaKuchG2JcIpNVKUosvajP2bbxDKnyEHWYJ1JujUXDSNt4 q6BoeTKDBHglSIIDvSy6RJj9pMV4lBk7UMWlTPC/4aC7LW0CY/pQUVhQrFZW4sVu G3TSO7oZJKlboVYxkbjhR+YVpM/4nv3jYW02gK5a6lw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=HSl4cO eylKJWGZ1gRfcpgzkKgRGUpcow+/PQb70GWe4=; b=j63DN7o0MmyWYmkAsVZJXw 12a6yCEGIoNtkAsUPmPxnF2mOntwW6Jsiv15m5VVFYBPtJFgY9lTOGRgOEWLh70Z fjSITzgZ+mzUzw/llYKC9SUuEgeQG3RyjrJN6VmkSWDg6wnnIbNFq/PD4W7VtBs4 BS/WexbMMlTrA3htZ84/+TPuHI4BDVEbfq+42s+g6lOn3/NCW8ooAhOTb6ITiDos trXXktVhRt12OBLT/nE66RGLfAZZQxSSW0/dV8iwubvn7QdRZOlGEAcpye/+z+oG 14u8TAGtwy98dyhC2UflTyk6r5tmjU2fxejGia/H1RAmCgwX+9uG1Iqg8zSrWQLw == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedtledrjeejgdehgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthenuceurghilhhouhhtmecufedt tdenucesvcftvggtihhpihgvnhhtshculddquddttddmnegfrhhlucfvnfffucdlfedtmd enucfjughrpeffhffvuffkfhggtggujgfofgesthdtredtofervdenucfhrhhomhepfdfv ohgsihhnucevrdcujfgrrhguihhnghdfuceomhgvsehtohgsihhnrdgttgeqnecukfhppe duvddurdeggedrvddvjedrudehjeenucfrrghrrghmpehmrghilhhfrhhomhepmhgvseht ohgsihhnrdgttgenucevlhhushhtvghrufhiiigvpedu X-ME-Proxy: Received: from localhost (ppp121-44-227-157.bras2.syd2.internode.on.net [121.44.227.157]) by mail.messagingengine.com (Postfix) with ESMTPA id E175CE412D; Thu, 31 Jan 2019 21:58:19 -0500 (EST) Date: Fri, 1 Feb 2019 13:58:13 +1100 From: "Tobin C. Harding" To: Matthew Wilcox Cc: "Tobin C. Harding" , Christoph Lameter , Pekka Enberg , David Rientjes , Joonsoo Kim , Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] mm/slab: Increase width of first /proc/slabinfo column Message-ID: <20190201025813.GB29854@eros.localdomain> References: <20190201004242.7659-1-tobin@kernel.org> <20190201024310.GC26359@bombadil.infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190201024310.GC26359@bombadil.infradead.org> X-Mailer: Mutt 1.11.2 (2019-01-07) User-Agent: Mutt/1.11.2 (2019-01-07) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 31, 2019 at 06:43:10PM -0800, Matthew Wilcox wrote: > On Fri, Feb 01, 2019 at 11:42:42AM +1100, 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. > > I had a proposal some time ago to turn the slab name from being kmalloced > to being an inline 16 bytes (with some fun hacks for cgroups). I think > that's a better approach than permitting such long names. For example, > ext4_allocation_context could be shortened to ext4_alloc_ctx without > losing any expressivity. > > Let me know if you can't find that and I'll try to dig it up. Thanks Willy, I'll try and find it and bring it back to life. Cheers, Tobin.