Hi
Nice job, (horoshaya rabota)
Just two issue:
-I saw this patch is using a global variable which counts the number
pending requests: dm_async_pending.
I think that this variable should be allocated per dm_crypt session, i.e
for each crypt_config, since there can be
more then 2 consumers
On Sun, Sep 04, 2005 at 03:51:57PM +0300, Ronen Shitrit ([EMAIL PROTECTED])
wrote:
Hi
Hello, Ronen.
Nice job, (horoshaya rabota)
:) thank you.
Just two issue:
-I saw this patch is using a global variable which counts the number
pending requests: dm_async_pending.
I think that this
On Sun, Sep 04, 2005 at 10:41:02PM +0300, Ronen Shitrit ([EMAIL PROTECTED])
wrote:
Hi
What do you think about the second remark??
-I think that we might have a problem if a write operation will be
processed in parallel to a read operation, the read might wait for the
write to
Hi
Did you tried to format a large partition (let say 10G) encrypted by
dm-crypt with AES-CBC?
I'm trying this and I see, that write and read request are mixing
together.
Why? Cause in the current patch the Read is blocked until all its
fragments will be encrypted,
But the Write is not blocked
On Sun, Sep 04, 2005 at 11:27:24PM +0300, Ronen Shitrit ([EMAIL PROTECTED])
wrote:
Hi
I already ported this patch to the OCF, and I'm using it over the OCF.
I also don't see any issue with small partitions??
The crypt_convert API is called from 2 different places in the code:
1. For
Ronen Shitrit [EMAIL PROTECTED] wrote:
I think, Correct me if I'm wrong,
What you described below, is 1 session with few operations (using the
routing feature of the acrypto), but once the session/set of operations
are done, then the session is closed.
I see. You want the session to last
