From: Jari Ruusu <jariruusu@users.sourceforge.net>
To: Ben Slusky <sluskyb@paranoiacs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove useless highmem bounce from loop/cryptoloop
Date: Thu, 30 Oct 2003 20:14:30 +0200 [thread overview]
Message-ID: <3FA15506.B9B76A5D@users.sourceforge.net> (raw)
In-Reply-To: 20031030134137.GD12147@fukurou.paranoiacs.org
Ben Slusky wrote:
> The attached patch changes the loop device transfer functions (including
> cryptoloop transfers) to accept page/offset pairs instead of virtual
> addresses, and removes the redundant kmaps in do_lo_send, do_lo_receive,
> and loop_transfer_bio. Per Andrew Morton's request a while back.
Cryptoloop is not the only user of loop transfer interface. Please don't
change that interface as it breaks code outside of mainline kernel.
Cryptoapi interface is quite broken. Your change extends that breakage to
loop transfer interface. Please don't do that.
Linus, please don't apply this patch.
--
Jari Ruusu 1024R/3A220F51 5B 4B F9 BB D3 3F 52 E9 DB 1D EB E3 24 0E A9 DD
next prev parent reply other threads:[~2003-10-30 18:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 13:41 [PATCH] remove useless highmem bounce from loop/cryptoloop Ben Slusky
2003-10-30 18:14 ` Jari Ruusu [this message]
2003-10-30 21:30 ` Andrew Morton
2003-10-31 0:52 ` Ben Slusky
2003-10-31 9:55 ` Andrew Morton
2003-10-31 9:55 ` Andrew Morton
2003-10-31 9:58 ` Andrew Morton
2003-11-13 3:06 ` Ben Slusky
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
2003-10-31 12:15 ` [PATCH] remove useless highmem bounce from loop/cryptoloop Jari Ruusu
2003-10-31 13:02 ` Jens Axboe
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=3FA15506.B9B76A5D@users.sourceforge.net \
--to=jariruusu@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sluskyb@paranoiacs.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