From: Jens Axboe <jens.axboe@oracle.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
Cc: Brent Baccala <cosine@freesoft.org>, linux-kernel@vger.kernel.org
Subject: Re: async I/O seems to be blocking on 2.6.15
Date: Fri, 10 Nov 2006 10:24:57 +0100 [thread overview]
Message-ID: <20061110092456.GO4527@kernel.dk> (raw)
In-Reply-To: <000001c701e9$a1435260$ff0da8c0@amr.corp.intel.com>
On Mon, Nov 06 2006, Chen, Kenneth W wrote:
> I haven't done the measurement whether the time to submit I/O grows
> linearly with respect to I/O size. Most likely it will. If it is
> not, then we might have a scaling problem (though I don't believe we
> have this problem).
I would not expect it to, but ran a simple test to check submission
times from 32KiB to 2MiB:
Size Time (usecs)
----------------------------
2MiB 223
1MiB 112
512KiB 56
256KiB 29
128KiB 14
32KiB 4
(note that I skipped 64KiB, things got boring). That clearly shows a
linear increase in time, so no scaling problem there.
--
Jens Axboe
next prev parent reply other threads:[~2006-11-10 9:22 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
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 [this message]
-- 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=20061110092456.GO4527@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=cosine@freesoft.org \
--cc=kenneth.w.chen@intel.com \
--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.