From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.server123.net (Postfix) with ESMTPS for ; Mon, 3 Aug 2020 06:26:03 +0200 (CEST) Received: from cmgw11.unifiedlayer.com (unknown [10.9.0.11]) by gproxy4.mail.unifiedlayer.com (Postfix) with ESMTP id 606AA175AAF for ; Sun, 2 Aug 2020 22:02:06 -0600 (MDT) Received: from 116-240-66-4.sta.dodo.net.au ([116.240.66.4]:53980 helo=monster) by just58.justhost.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from ) id 1k2Rfo-0016h9-IT for dm-crypt@saout.de; Sun, 02 Aug 2020 22:02:05 -0600 Message-ID: <877d3378399ec6a52c049b99ecb19cfa05a78d56.camel@erwinvanlonden.net> From: Erwin van Londen Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-CHz6urzJO6d8QF72TdLv" Date: Mon, 03 Aug 2020 13:56:46 +1000 MIME-Version: 1.0 Subject: [dm-crypt] IO performance implications using dm-crypt List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: dm-crypt@saout.de --=-CHz6urzJO6d8QF72TdLv Content-Type: multipart/alternative; boundary="=-tH2NDZt9uqyHz9RnbFI8" --=-tH2NDZt9uqyHz9RnbFI8 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello All, I've been searching for information with regards to performance implications by using dm-crypt on a IO level. I know that a fair amount is available that highlight the CPU overhead and some benchmarks seem to be around but that's not really what I'm after. Obviously a delay on processing on crypto/cpu side will at some stage hamper overall IO capabilities. Does anyone have any reference to numbers that show direct impact on an IOPS side when system-resources like CPU and memory are not really at play? Your help is much appreciated. Kind regards, Erwin --=-tH2NDZt9uqyHz9RnbFI8 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
Hello All,

I've been searching for inform= ation with regards to performance implications by using dm-crypt on a IO le= vel. I know that a fair amount is available that highlight the CPU overhead= and some benchmarks seem to be around but that's not really what I'm after= . Obviously a delay on processing on crypto/cpu side will at some stage ham= per overall IO capabilities. Does anyone have any reference to numbers that= show direct impact on an IOPS side when system-resources like CPU and memo= ry are not really at play?

Your help is much appre= ciated.

Kind regards,
Erwin
= --=-tH2NDZt9uqyHz9RnbFI8-- --=-CHz6urzJO6d8QF72TdLv Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- iQFNBAABCAA3FiEE7+LwJsk9ghq3YmbRRQ4nq36ha1AFAl8niv4ZHGVyd2luQGVy d2ludmFubG9uZGVuLm5ldAAKCRBFDierfqFrUOLyB/9CFy1vG3hi8EU7xHalqsFd ZQ5eD+BOAW4fP32TZPcLWuQdMoM7D8s44vVlgsuE988ktY3Dhocc9b8HnjWR01SR bGeXJvDmKvu6onlaJRy+v5RbZ+fXHgcuQ6M2ZHRhL5+YTqkVM7mZN8tVHh3k163X Biu2w6mR/AboftdFLJveoINuJWutr+ssHDF4jwPF3kMgGRAMWty+/ngsk9s57Acv HeWi12/bhqsCfZBzo9dOzv5pK1ze0n3dpAVAYV8E5ZRGOIz131X5tWVvnnP2huvd Ev62UBcm2UnmCPCUpmuiOwija3gYnaGZvrgDsNea3qzgwmmFaI3F7LY2iwvft8oT =H7R0 -----END PGP SIGNATURE----- --=-CHz6urzJO6d8QF72TdLv--