From: Mike Travis <travis@sgi.com>
To: Paul Jackson <pj@sgi.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
Alan.Brunelle@hp.com, linux-kernel@vger.kernel.org,
npiggin@suse.de, dgc@sgi.com, arjan@linux.intel.com
Subject: Re: IO queueing and complete affinity w/ threads: Some results
Date: Tue, 19 Feb 2008 13:31:36 -0800 [thread overview]
Message-ID: <47BB4AB8.9020509@sgi.com> (raw)
In-Reply-To: <20080219151418.97557f0f.pj@sgi.com>
Paul Jackson wrote:
> Jens wrote:
>> My main worry with the current code is the ->lock in the per-cpu
>> completion structure.
>
> Drive-by-comment here: Does the patch posted later this same day by Mike Travis:
>
> [PATCH 0/2] percpu: Optimize percpu accesses v3
>
> help with this lock issue any? (I have no real clue here -- just connecting
> up the pretty colored dots ;).
>
I'm not sure of the context here but a big motivation for doing the
zero-based per_cpu variables was to optimize access to the local
per cpu variables to one instruction, reducing the need for locks.
-Mike
next prev parent reply other threads:[~2008-02-19 21:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 20:56 IO queueing and complete affinity w/ threads: Some results Alan D. Brunelle
2008-02-12 20:56 ` Alan D. Brunelle
2008-02-12 22:08 ` Alan D. Brunelle
2008-02-12 22:26 ` Alan D. Brunelle
2008-02-13 15:35 ` Alan D. Brunelle
2008-02-14 15:36 ` Alan D. Brunelle
2008-02-18 12:37 ` Jens Axboe
2008-02-18 13:33 ` Andi Kleen
2008-02-18 14:16 ` Jens Axboe
2008-02-19 1:49 ` Nick Piggin
2008-02-19 21:14 ` Paul Jackson
2008-02-19 21:31 ` Mike Travis [this message]
2008-02-20 8:08 ` Jens Axboe
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=47BB4AB8.9020509@sgi.com \
--to=travis@sgi.com \
--cc=Alan.Brunelle@hp.com \
--cc=arjan@linux.intel.com \
--cc=dgc@sgi.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=pj@sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.