From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751569AbcHGIm4 (ORCPT ); Sun, 7 Aug 2016 04:42:56 -0400 Received: from mail-lf0-f65.google.com ([209.85.215.65]:35217 "EHLO mail-lf0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751399AbcHGImz (ORCPT ); Sun, 7 Aug 2016 04:42:55 -0400 Date: Sun, 7 Aug 2016 11:42:50 +0300 From: Alexey Dobriyan To: Al Viro Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] proc: much faster /proc/vmstat Message-ID: <20160807084249.GA1871@p183.telecom.by> References: <20160806125455.GA1187@p183.telecom.by> <20160807013510.GM2356@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160807013510.GM2356@ZenIV.linux.org.uk> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Aug 07, 2016 at 02:35:13AM +0100, Al Viro wrote: > On Sat, Aug 06, 2016 at 03:54:56PM +0300, Alexey Dobriyan wrote: > > [sprintf sucks, let's convert numbers manually] > > > --- a/mm/vmstat.c > > +++ b/mm/vmstat.c > > @@ -1592,7 +1592,10 @@ static int vmstat_show(struct seq_file *m, void *arg) > > { > > unsigned long *l = arg; > > unsigned long off = l - (unsigned long *)m->private; > > - seq_printf(m, "%s %lu\n", vmstat_text[off], *l); > > + > > + seq_puts(m, vmstat_text[off]); > > + seq_put_decimal_ull(m, ' ', *l); > > + seq_putc(m, '\n'); > > return 0; > > } > > If that manages to be a hotspot, we really should > * educate the wankers responsible for the userland code in question, > until they repent and cease committing such abominations. I'll get right on that. > * look into fixing vsnprintf(). > > Seriously, what the hell is vsnprintf() doing that takes so much time? It's > not as if it was a complex format anyway. WTF is going on there? Where is > it spending that much time? 1. format_decode() is busy looking for format specifier: 2 branches per character (not in this case, but in others) 2. approximately million branches while parsing format mini language and everywhere 3. just look at what string() does /proc/vmstat is good case because most of its content are strings But the patch will still be faster.