From: Momchil Velikov <velco@fadata.bg>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Copying to loop device hangs up everything
Date: 18 Dec 2001 23:26:54 +0200 [thread overview]
Message-ID: <876674i5i9.fsf@fadata.bg> (raw)
In-Reply-To: <Pine.LNX.4.21.0112181757460.4821-100000@freak.distro.conectiva>
In-Reply-To: <Pine.LNX.4.21.0112181757460.4821-100000@freak.distro.conectiva>
>>>>> "Marcelo" == Marcelo Tosatti <marcelo@conectiva.com.br> writes:
Marcelo> Momchil,
Marcelo> Your fix does not look right. We _have_ to sync pages at
Marcelo> sync_page_buffers(), we cannot "ignore" them.
>> Sure, we don't ignore them, we just don't _wait_ for them, because
>> maybe _we_ are the one to write them.
Marcelo> What if we are not ?
Hmm, looks like we pray to find another immediately usable page, to
finish _this_ request first, and then we will ``loop_get_bh'' the
buffer we just avoided waiting on and sync it.
Hmm, _maybe_ it is a good idea buffers submitted for IO by the
loopback threads to themselves go _in front_ of the loopback queue ?
Regards,
-velco
next prev parent reply other threads:[~2001-12-18 21:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 3:40 Copying to loop device hangs up everything David Gomez
2001-12-16 4:00 ` Dave Jones
2001-12-16 11:41 ` David Gomez
2001-12-16 16:53 ` Momchil Velikov
2001-12-16 19:42 ` David Gomez
2001-12-16 19:50 ` Momchil Velikov
2001-12-16 21:52 ` Momchil Velikov
2001-12-18 19:46 ` Marcelo Tosatti
2001-12-18 20:54 ` Momchil Velikov
2001-12-18 19:57 ` Marcelo Tosatti
2001-12-18 21:26 ` Momchil Velikov [this message]
[not found] ` <3C1FC254.525B9108@zip.com.au>
[not found] ` <3C1FCB96.83E49ECB@zip.com.au>
[not found] ` <3C204C4F.C989AD71@zip.com.au>
2001-12-19 13:42 ` Andrea Arcangeli
2001-12-20 7:41 ` Andrew Morton
2001-12-20 11:27 ` Andrea Arcangeli
2001-12-20 11:34 ` Andrea Arcangeli
2001-12-17 3:30 ` Dave Jones
-- strict thread matches above, loose matches on Subject: below --
2001-12-20 21:05 Momchil Velikov
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=876674i5i9.fsf@fadata.bg \
--to=velco@fadata.bg \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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.