public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* patch: loop remapper
@ 2000-11-16 17:25 Jens Axboe
  2000-11-17 18:24 ` Marc Mutz
  0 siblings, 1 reply; 2+ messages in thread
From: Jens Axboe @ 2000-11-16 17:25 UTC (permalink / raw)
  To: Linux Kernel

Hi,

This patch makes loop work like a block remapper. It was started
yesterday due to me trying to solve the (chronic) loop deadlocks
that have plauged 2.3/2.4 for ages. It has several advantages over
the old request handling:

* loop doesn't eat request slots. This alone saves run time memory
  requirements (standard is 256 request slots per queue)
* don't have to fight block layer wrt merging, plugging, etc
* much faster, loop doesn't serialize I/O requests anymore. This also
  allows the target device elevator to work a lot better.

People having loop problems, please give this a go. It may still have
a few 'issues', but I bet they are solvable now. If you are asking
'why' when seeing this patch, I urge you to

vi drivers/block/loop.c
/do_lo_request

and have a barf bag ready.

The builtin transfer functions (none and xor) work with the changes,
but external crypto additions may not. The reason is that the raw
buf and loop buf passed to them can now be identical (the previous
version always used getblk() to get a new buffer to work on).

*.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.0-test11-pre5/loop-remap-2.bz2

-- 
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: patch: loop remapper
  2000-11-16 17:25 patch: loop remapper Jens Axboe
@ 2000-11-17 18:24 ` Marc Mutz
  0 siblings, 0 replies; 2+ messages in thread
From: Marc Mutz @ 2000-11-17 18:24 UTC (permalink / raw)
  To: Jens Axboe; +Cc: Linux Kernel

Jens Axboe wrote:
> 
<snip>
> 
> The builtin transfer functions (none and xor) work with the changes,
> but external crypto additions may not. The reason is that the raw
> buf and loop buf passed to them can now be identical (the previous
> version always used getblk() to get a new buffer to work on).
> 
<snip>

The crypto-api from the international kernel patch has recently defined
that the encryption functions contained in it must be able to encrypt
in-place. This maps directly to the loop-gen driver, so I don't see a
problem here. (Other than that there is no real patch-int-2.4.x out
there yet). However, the ciphers have not been checked to conform to
that definition.

Marc

-- 
Marc Mutz <Marc@Mutz.com>     http://EncryptionHOWTO.sourceforge.net/
University of Bielefeld, Dep. of Mathematics / Dep. of Physics

PGP-keyID's:   0xd46ce9ab (RSA), 0x7ae55b9e (DSS/DH)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2000-11-17 19:12 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2000-11-16 17:25 patch: loop remapper Jens Axboe
2000-11-17 18:24 ` Marc Mutz

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox