From: Marc-Christian Petersen <m.c.p@wolk-project.de>
To: Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org, Chris Mason <mason@suse.com>
Subject: Re: 2.4.22pre6aa1
Date: Fri, 18 Jul 2003 00:13:38 +0200 [thread overview]
Message-ID: <200307180013.38078.m.c.p@wolk-project.de> (raw)
In-Reply-To: <20030717102857.GA1855@dualathlon.random>
On Thursday 17 July 2003 12:28, Andrea Arcangeli wrote:
Hi Andrea,
> Only in 2.4.22pre6aa1: 00_elevator-lowlatency-1
> Only in 2.4.22pre6aa1: 00_elevator-read-reservation-axboe-2l-1
Hmm, this is now my first day testing out .22-pre6 and .22-pre6aa1 with the
new I/O stall fixes. At a first look & feel it's very good, but I've noticed
a side effect (if it can be called so):
VMware4 Workstation
-------------------
2.4.22-pre[6|6aa1]: ~ 1 minute 02 seconds from: Start this virtual machine ...
2.4.22-pre2 : ~ 30 seconds from: Start this virtual machine ...
... to start up Windows 2000 Professional completely.
Well, personally I don't care about the slowdown of vmware startup with a VM
but there may be many other slowdows?!
ciao, Marc
next prev parent reply other threads:[~2003-07-17 22:01 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 10:28 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 10:42 ` 2.4.22pre6aa1 ooyama eiichi
2003-07-17 10:52 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 10:53 ` 2.4.22pre6aa1 ooyama eiichi
2003-07-17 15:42 ` 2.4.22pre6aa1 Dave Jones
2003-07-17 20:31 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 22:13 ` Marc-Christian Petersen [this message]
2003-07-17 22:26 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-17 22:27 ` 2.4.22pre6aa1 Mike Fedyk
2003-07-17 22:32 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:30 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-17 22:50 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 0:30 ` 2.4.22pre6aa1 Chris Mason
2003-07-22 12:28 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-22 14:04 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 5:47 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-22 13:34 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-22 13:59 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-24 12:27 ` 2.4.22pre6aa1 Marc-Christian Petersen
2003-07-24 14:14 ` 2.4.22pre6aa1 Chris Mason
2003-07-18 18:18 ` 2.4.22pre6aa1 Christoph Hellwig
2003-07-18 22:27 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 22:48 ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-18 22:53 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 23:04 ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-18 23:12 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-18 23:53 ` 2.4.22pre6aa1 William Lee Irwin III
2003-07-19 0:04 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-23 11:21 2.4.22pre6aa1 Sergey S. Kostyliov
2003-07-25 5:28 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-07-25 11:10 ` 2.4.22pre6aa1 Sergey S. Kostyliov
2003-07-25 19:02 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-08-03 17:12 ` 2.4.22pre6aa1 Sergey S. Kostyliov
2003-08-16 11:56 ` 2.4.22pre6aa1 Andrea Arcangeli
2003-08-16 13:54 ` 2.4.22pre6aa1 Hugh Dickins
2003-08-16 14:00 ` 2.4.22pre6aa1 Hugh Dickins
2003-08-16 14:50 ` 2.4.22pre6aa1 Sergey S. Kostyliov
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=200307180013.38078.m.c.p@wolk-project.de \
--to=m.c.p@wolk-project.de \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).