From: Andi Kleen <ak@muc.de>
To: Christophe Saout <christophe@saout.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] loop.c patches, take two
Date: Mon, 22 Dec 2003 02:21:11 +0100 [thread overview]
Message-ID: <m31xqx7im0.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <15kfk-vj-1@gated-at.bofh.it> (Christophe Saout's message of "Sun, 21 Dec 2003 23:30:07 +0100")
Christophe Saout <christophe@saout.de> writes:
> Am So, den 21.12.2003 schrieb Mika Penttilä um 21:49:
>
>> Yet another Big Loop Patch... :)
>>
>> It's not obvious which parts are bug fixes, and which performance
>> improvements. What exactly breaks loops on journalling filesystems, and
>> how do you solve it?
>
> What about dropping block device backed support for the loop driver
> altogether? We now have a nice device mapper in the 2.6 kernel. I don't
Device Mapper doesn't support cryptographic transformations.
-Andi
next parent reply other threads:[~2003-12-22 1:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MllE.6qa.7@gated-at.bofh.it>
[not found] ` <MpyW.3Ub.9@gated-at.bofh.it>
[not found] ` <MsGq.8cN.1@gated-at.bofh.it>
[not found] ` <MvO6.47g.7@gated-at.bofh.it>
[not found] ` <MEf3.8oB.13@gated-at.bofh.it>
[not found] ` <MROA.319.5@gated-at.bofh.it>
[not found] ` <NxkP.4kY.17@gated-at.bofh.it>
[not found] ` <15hUp-58e-21@gated-at.bofh.it>
[not found] ` <15iGH-6hd-17@gated-at.bofh.it>
[not found] ` <15kfk-vj-1@gated-at.bofh.it>
2003-12-22 1:21 ` Andi Kleen [this message]
2003-12-22 1:30 ` [PATCH] loop.c patches, take two Christophe Saout
2003-10-30 13:41 [PATCH] remove useless highmem bounce from loop/cryptoloop Ben Slusky
2003-10-30 18:14 ` Jari Ruusu
2003-10-30 21:30 ` Andrew Morton
2003-10-31 0:52 ` Ben Slusky
2003-10-31 9:55 ` Andrew Morton
2003-11-01 0:26 ` Ben Slusky
2003-11-02 20:46 ` Ben Slusky
2003-12-21 19:55 ` [PATCH] loop.c patches, take two Ben Slusky
2003-12-21 20:07 ` Ben Slusky
2003-12-21 20:49 ` Mika Penttilä
2003-12-21 21:12 ` Ben Slusky
2003-12-21 23:00 ` Mika Penttilä
2003-12-21 23:05 ` Ben Slusky
2003-12-21 23:51 ` Mika Penttilä
2003-12-21 22:01 ` Christophe Saout
2003-12-22 6:33 ` Andrew Morton
2003-12-22 23:32 ` Ben Slusky
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=m31xqx7im0.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=christophe@saout.de \
--cc=linux-kernel@vger.kernel.org \
/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