From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] why nbytes for block cipher encrypt/decrypt is only 512 bytes
Date: Fri, 20 Apr 2012 12:22:44 +0200 [thread overview]
Message-ID: <20120420102244.GA18629@tansi.org> (raw)
In-Reply-To: <CAPihpKBpGL7SncafRNwZ+eJk2Ck83KWZg=0BmooYeconXHLGhA@mail.gmail.com>
I think you cannot. As long as the block-size for the IV scheme
is 512 bytes, you are stuck with encrypting 512 bytes at a time,
as they have their own IV.
Arno
On Fri, Apr 20, 2012 at 05:28:54PM +0800, Rodel Miguel wrote:
> Hi,
>
> I am implementing a hardware encryption driver but I am having some
> performance issues. One of the areas of performance improvement that I am
> thinking is to increase the number of bytes (unsigned int nbytes) that my
> block cipher driver's encrypt/decrypt function gets; from 512 to 4096
> bytes. My hardware can be maximized to 4kbytes. Do you have any
> suggestions how I can maximize the en/decrypt performance by getting more
> than 512 bytes of data every time the block cipher's encrypt/decrypt is
> called?
>
> Thank you very much for your help!
>
> Kind Regards,
> Rodel
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-04-20 10:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 9:28 [dm-crypt] why nbytes for block cipher encrypt/decrypt is only 512 bytes Rodel Miguel
2012-04-20 10:22 ` Arno Wagner [this message]
2012-04-20 10:55 ` Rodel Miguel
2012-04-20 11:35 ` Milan Broz
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=20120420102244.GA18629@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/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.