All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: Thanos Makatos <mcatos@ics.forth.gr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Inexplicable I/O latency using worker threads
Date: Fri, 12 Dec 2008 12:46:52 -0500	[thread overview]
Message-ID: <4942A38C.7050907@redhat.com> (raw)
In-Reply-To: <4942314E.80408@ics.forth.gr>

Thanos Makatos wrote:
> Hello all.
> 
> I am facing a weird problem with a virtual block driver I made concerning excessive I/O latency.
> 
> My block driver intercepts requests and redirects them to a real block device,
> but not just be setting the bio->bi_bdev field, I create new bios.
> 
> Anyway, my problem is that for load balancing reasons I need per-CPU worker threads
> where I enqueue requests and let them do all the work. If I use 2 threads in a round
> robin manner (request 1 served by CPU 0, 2 by CPU1, 3 by CPU0 and so on), performance
> is inexplicably low.
> 
> If I choose only one CPU to act as a worker the problem is gone. The difference of measured
> I/O latency is more than 30 times.
> 
> What could be happening?
> 
> I'm using a vanilla 2.6.18.8.
> 
> Thanx in advance.

a) I/O scheduling
b) lock contention

Do you really need to load balance I/O to a single bdev across multiple CPUs? 
Disk I/O generally isn't very CPU-intensive.

-- Chris

  reply	other threads:[~2008-12-12 17:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12  9:39 Inexplicable I/O latency using worker threads Thanos Makatos
2008-12-12 17:46 ` Chris Snook [this message]
2008-12-13 12:44   ` Thanos McAtos

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=4942A38C.7050907@redhat.com \
    --to=csnook@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcatos@ics.forth.gr \
    /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.