From: Jens Axboe <jens.axboe@oracle.com>
To: Richard Kennedy <richard@rsk.demon.co.uk>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] block: don't access jiffies when initialising io_context
Date: Mon, 1 Mar 2010 10:56:56 +0100 [thread overview]
Message-ID: <20100301095656.GV5768@kernel.dk> (raw)
In-Reply-To: <1267437213.2127.18.camel@localhost>
On Mon, Mar 01 2010, Richard Kennedy wrote:
> As the comment says the initial value of last_waited is never used, so
> there is no need to initialise it with the current jiffies. Jiffies is
> hot enough without accessing it for no reason.
Applied, though it will not make a huge difference in any way.
alloc_io_context() only gets called the first time a process does IO, so
it's not a hot path.
>
> Signed-off-by: Richard Kennedy <richard@rsk.demon.co.uk>
> ---
> patch against 2.6.33
> compiled & tested on x86_64
>
> diff --git a/block/blk-ioc.c b/block/blk-ioc.c
> index 98e6bf6..3f65c8a 100644
> --- a/block/blk-ioc.c
> +++ b/block/blk-ioc.c
> @@ -91,7 +91,7 @@ struct io_context *alloc_io_context(gfp_t gfp_flags, int node)
> spin_lock_init(&ret->lock);
> ret->ioprio_changed = 0;
> ret->ioprio = 0;
> - ret->last_waited = jiffies; /* doesn't matter... */
> + ret->last_waited = 0; /* doesn't matter... */
> ret->nr_batch_requests = 0; /* because this is 0 */
> INIT_RADIX_TREE(&ret->radix_root, GFP_ATOMIC | __GFP_HIGH);
> INIT_HLIST_HEAD(&ret->cic_list);
>
>
--
Jens Axboe
prev parent reply other threads:[~2010-03-01 9:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 9:53 [PATCH] block: don't access jiffies when initialising io_context Richard Kennedy
2010-03-01 9:56 ` Jens Axboe [this message]
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=20100301095656.GV5768@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@rsk.demon.co.uk \
/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