From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dmitry Voytik <voytikd@gmail.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] fs: seq_file: optimize seq_pad()
Date: Wed, 10 Sep 2014 14:21:23 +0100 [thread overview]
Message-ID: <20140910132123.GZ7996@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1410340819-18338-1-git-send-email-voytikd@gmail.com>
On Wed, Sep 10, 2014 at 01:20:19PM +0400, Dmitry Voytik wrote:
> Use seq_putc() instead of seq_printf() in seq_pad() because the
> former is faster.
_Solitary_ seq_putc() is certainly going to be faster, but that loop...
Do you have profiling results, or is it just an apriori "printf must
be sloooowwww"?
next prev parent reply other threads:[~2014-09-10 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 9:20 [PATCH] fs: seq_file: optimize seq_pad() Dmitry Voytik
2014-09-10 13:21 ` Al Viro [this message]
2014-09-10 14:20 ` Dmitry Voytik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140910132123.GZ7996@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=voytikd@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).