From: Paul Clements <paul.clements@steeleye.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
linux-kernel@vger.kernel.org, nbd-general@lists.sourceforge.net,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [PATCH 1/1] NBD: make nbd default to deadline I/O scheduler
Date: Fri, 08 Feb 2008 13:41:20 -0500 [thread overview]
Message-ID: <47ACA250.1010404@steeleye.com> (raw)
In-Reply-To: <20080208101151.935b575c.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Fri, 8 Feb 2008 09:33:41 -0800 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
>> On Fri, 08 Feb 2008 11:47:42 -0500 Paul Clements wrote:
>>
>>> There have been numerous reports of problems with nbd and cfq. Deadline
>>> gives better performance for nbd, anyway, so let's use it by default.
>
> Please define "problems". If it's just "slowness" then we can live with
> that, but I'd hope that Jens is aware and that it's understood.
>
> It it's "hangs" or "oopses" then we panic.
The two problems I have experienced (which may already be fixed):
1) nbd hangs with cfq on RHEL 5 (2.6.18) -- this may well have been fixed
There's a similar debian bug that has been filed as well:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=447638
2) nbd performs about 10% better (the last time I tested) with deadline
vs. cfq (the overhead of cfq doesn't provide much advantage to nbd [not
being a real disk], and you end up going through the I/O scheduler on
the nbd server anyway, so it makes sense that deadline is better with nbd)
There have been posts to nbd-general mailing list about problems with
cfq and nbd also.
--
Paul
next prev parent reply other threads:[~2008-02-08 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 16:47 [PATCH 1/1] NBD: make nbd default to deadline I/O scheduler Paul Clements
2008-02-08 17:33 ` Randy Dunlap
2008-02-08 18:11 ` Andrew Morton
2008-02-08 18:41 ` Paul Clements [this message]
2008-02-08 20:45 ` Jens Axboe
2008-02-08 20:47 ` Jens Axboe
2008-02-08 21:23 ` Paul Clements
2008-02-08 22:02 ` Andrew Morton
2008-02-09 13:30 ` Paul Clements
2008-02-12 23:16 ` Andrew Morton
2008-02-18 18:16 ` Jens Axboe
2008-02-18 23:50 ` Andrew Morton
2008-02-19 9:19 ` Jens Axboe
2008-02-19 9:24 ` Jens Axboe
2008-02-19 10:02 ` Andrew Morton
2008-02-19 10:05 ` Jens Axboe
2008-02-08 22:45 ` [Nbd] " Mike Snitzer
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=47ACA250.1010404@steeleye.com \
--to=paul.clements@steeleye.com \
--cc=akpm@linux-foundation.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd-general@lists.sourceforge.net \
--cc=randy.dunlap@oracle.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 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.