All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@us.ibm.com>
To: Jens Axboe <axboe@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Time sliced cfq with basic io priorities
Date: Wed, 15 Dec 2004 07:18:41 -0800	[thread overview]
Message-ID: <20041215151840.GA1265@us.ibm.com> (raw)
In-Reply-To: <20041215063628.GL3157@suse.de>

On Wed, Dec 15, 2004 at 07:36:28AM +0100, Jens Axboe wrote:
> On Tue, Dec 14 2004, Paul E. McKenney wrote:
> > If only one task is referencing the list at all, no need for RCU or for
> > any other synchronization mechanism.  If multiple threads are referencing
> > the list, I cannot find any pure readers.  If multiple threads are updating
> > the list, I don't see how they are excluding each other.
> > 
> > Any enlightenment available?  I most definitely need a clue here...
> 
> No, you are about right :-)
> 
> The RCU stuff can go again, because I moved everything to happen under
> the same task. The section under rcu_read_lock() is the reader, it just
> later on moved the hot entry to the front as well which does indeed mean
> it's buggy if there were concurrent updaters. So that's why it's in a
> state of being a little messy right now.
> 
> A note on the list itself - a task has a cfq_io_context per queue it's
> doing io against and it needs to be looked up when we this process
> queues io. The task sets this up itself on first io and tears this down
> on exit. So only the task itself ever updates or searches this list.

Whew!!!  I feel much better!

							Thanx, Paul

      reply	other threads:[~2004-12-15 15:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 12:50 [PATCH] Time sliced cfq with basic io priorities Jens Axboe
2004-12-13 13:09 ` Jens Axboe
2004-12-13 17:57   ` Jens Axboe
2004-12-14 13:37     ` Jens Axboe
2004-12-14 21:31       ` Paul E. McKenney
2004-12-15  6:36         ` Jens Axboe
2004-12-15 15:18           ` Paul E. McKenney [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=20041215151840.GA1265@us.ibm.com \
    --to=paulmck@us.ibm.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    /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.