From: Michael Tokarev <mjt@tls.msk.ru>
To: Wu Fengguang <wfg@mail.ustc.edu.cn>,
Michael Tokarev <mjt@tls.msk.ru>,
Ingo Oeser <ioe-lkml@rameria.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, Jens Axboe <axboe@suse.de>
Subject: Re: [PATCH 4/5] readahead: backoff on I/O error
Date: Mon, 12 Jun 2006 15:06:47 +0400 [thread overview]
Message-ID: <448D4AC7.4040009@tls.msk.ru> (raw)
In-Reply-To: <350074764.23563@ustc.edu.cn>
Wu Fengguang wrote:
[]
> Andrew:
> I was a bit afraid about that because I have no CDROM to try it out.
> But since Michael has tested it OK, it should be OK for the stable kernel.
Hmm.. I haven't "tested it OK" yet. I just ran a quick-n-dirty
check. Tomorrow I'll be in our office where I have more adequate
"test environment" for this stuff (different CD/DVD drives and
disks, some scratched), and I'll do some real testing.
Thanks.
/mjt
next prev parent reply other threads:[~2006-06-12 11:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 8:08 [PATCH 0/5] Adaptive readahead updates 2 Wu Fengguang
2006-06-09 8:08 ` Wu Fengguang
2006-06-09 8:08 ` [PATCH 1/5] readahead: no RA_FLAG_EOF on single page file Wu Fengguang
2006-06-09 8:08 ` Wu Fengguang
2006-06-09 8:08 ` [PATCH 3/5] readahead: call scheme - no fastcall for readahead_cache_hit() Wu Fengguang
2006-06-09 8:08 ` Wu Fengguang
2006-06-09 8:08 ` [PATCH 4/5] readahead: backoff on I/O error Wu Fengguang
2006-06-09 8:08 ` Wu Fengguang
2006-06-10 18:33 ` Ingo Oeser
2006-06-10 19:48 ` Michael Tokarev
2006-06-12 1:12 ` Wu Fengguang
2006-06-12 1:12 ` Wu Fengguang
2006-06-12 3:43 ` Andrew Morton
2006-06-12 11:06 ` Michael Tokarev [this message]
2006-06-17 6:38 ` Michael Tokarev
2006-06-17 7:00 ` Michael Tokarev
2006-06-09 8:08 ` [PATCH 5/5] readahead: remove size limit on read_ahead_kb Wu Fengguang
2006-06-09 8:08 ` Wu Fengguang
-- strict thread matches above, loose matches on Subject: below --
2006-06-11 5:34 [PATCH 4/5] readahead: backoff on I/O error Just Marc
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=448D4AC7.4040009@tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=ioe-lkml@rameria.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wfg@mail.ustc.edu.cn \
/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.