public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Brent Baccala <cosine@freesoft.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: async I/O seems to be blocking on 2.6.15
Date: Mon, 6 Nov 2006 11:43:50 +0100	[thread overview]
Message-ID: <20061106104350.GR13555@kernel.dk> (raw)
In-Reply-To: <Pine.LNX.4.64.0611060136250.4220@debian.freesoft.org>

On Mon, Nov 06 2006, Brent Baccala wrote:
> On Sun, 5 Nov 2006, Jens Axboe wrote:
> 
> >On Fri, Nov 03 2006, Brent Baccala wrote:
> >>
> >>Does 7 microseconds seem a bit excessive for an io_submit (and a
> >>gettimeofday)?
> >
> >I guess you mean miliseconds, not microseconds. 7 miliseconds seems way
> >too long. I repeated your test here, and the 100 submits take 97000
> >microseconds here - or 97 miliseconds. So that's a little less than 1
> >msec per io_submit. Still pretty big. You can experiment with oprofile
> >to profile where the kernel spends its time in that period.
> >
> >-- 
> >Jens Axboe
> >
> 
> Yes, of course, milliseconds.  I have enough other problems with this
> program (measured in minutes, and no mistake that) that I doubt I'll
> be profiling the kernel any time soon, but thank you for your help.
> 
> More than anything else, you've made me understand that I can't just
> fire off a bunch of async requests like I'm tossing peanuts across the
> table.  I've really got to pay attention to what's in that kernel
> queue and how it gets managed.

Yeah, I'm afraid so. We really should be returning EAGAIN or something
like that for the congested condition, though.

-- 
Jens Axboe


  reply	other threads:[~2006-11-06 10:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03  8:23 async I/O seems to be blocking on 2.6.15 Brent Baccala
2006-11-03 12:20 ` Jens Axboe
2006-11-03 15:58   ` Brent Baccala
2006-11-03 16:02     ` Jens Axboe
2006-11-03 17:09       ` Brent Baccala
2006-11-03 17:30       ` Brent Baccala
2006-11-05 12:15         ` Jens Axboe
2006-11-06  6:42           ` Brent Baccala
2006-11-06 10:43             ` Jens Axboe [this message]
2006-11-06 15:52               ` Phillip Susi
2006-11-06 16:02                 ` Jens Axboe
2006-11-06 17:04                   ` Phillip Susi
2006-11-06 17:10                     ` Jens Axboe
2006-11-06 21:22           ` Chen, Kenneth W
2006-11-07  7:26             ` Jens Axboe
2006-11-07 21:02             ` Bill Davidsen
2006-11-10  9:24             ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2006-11-07  0:03 Brent Baccala
2006-11-07  0:24 ` Chen, Kenneth W
2006-11-07  7:29 ` 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=20061106104350.GR13555@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=cosine@freesoft.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox