From: Laurent Vivier <Laurent.Vivier@bull.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: Paul.Clements@steeleye.com, nbd-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow NBD to be used locally
Date: Sat, 02 Feb 2008 16:26:11 +0100 [thread overview]
Message-ID: <1201965971.4591.13.camel@frecb07144> (raw)
In-Reply-To: <20080202112336.GB5362@elf.ucw.cz>
Le samedi 02 février 2008 à 12:23 +0100, Pavel Machek a écrit :
> On Fri 2008-02-01 14:25:32, Laurent Vivier wrote:
> > This patch allows Network Block Device to be mounted locally.
>
> What is local nbd good for? Use loop instead...
It allows to write userlevel block device. In my case, I can mount disk
image of Qemu (qcow2, vmdk, ...).
> > It creates a kthread to avoid the deadlock described in NBD tools documentation.
> > So, if nbd-client hangs waiting pages, the kblockd thread can continue its
> > work and free pages.
>
> Hmm, and if there are no other pages that can be freed? Unlikely, but
> can happen AFAICT.
Correct. The patch improves the NBD behavior even if it is not perfect.
And I think if no other page can be freed your system is in very bad
move ;-)
Laurent
--
----------------- Laurent.Vivier@bull.net ------------------
"La perfection est atteinte non quand il ne reste rien à
ajouter mais quand il ne reste rien à enlever." Saint Exupéry
next prev parent reply other threads:[~2008-02-02 15:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 13:25 [PATCH] Allow NBD to be used locally Laurent Vivier
2008-02-02 11:23 ` Pavel Machek
2008-02-02 11:52 ` Jan Engelhardt
2008-02-02 15:26 ` Laurent Vivier [this message]
2008-02-02 16:13 ` Miklos Szeredi
2008-02-02 20:54 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-02-02 14:40 devzero
2008-02-02 16:57 ` Jan Engelhardt
2008-02-02 17:31 devzero
2008-02-03 0:54 ` Jan Engelhardt
2008-02-03 6:02 ` Kyle Moffett
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=1201965971.4591.13.camel@frecb07144 \
--to=laurent.vivier@bull.net \
--cc=Paul.Clements@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd-general@lists.sourceforge.net \
--cc=pavel@ucw.cz \
/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.