linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andre Glover <andre.glover@linux.intel.com>
To: tom.zanussi@linux.intel.com, minchan@kernel.org,
	senozhatsky@chromium.org, hannes@cmpxchg.org,
	yosryahmed@google.com, nphamcs@gmail.com,
	chengming.zhou@linux.dev, herbert@gondor.apana.org.au,
	davem@davemloft.net, fenghua.yu@intel.com, dave.jiang@intel.com
Cc: wajdi.k.feghali@intel.com, james.guilford@intel.com,
	vinodh.gopal@intel.com, bala.seshasayee@intel.com,
	heath.caldwell@intel.com, kanchana.p.sridhar@intel.com,
	andre.glover@linux.intel.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, 21cnbao@gmail.com, ryan.roberts@arm.com,
	linux-crypto@vger.kernel.org, dmaengine@vger.kernel.org
Subject: [RFC PATCH 2/3] crypto: add by_n attribute to acomp_req
Date: Wed,  1 May 2024 14:46:28 -0700	[thread overview]
Message-ID: <8fe04e86f0907588d210885ac91965960f97f450.1714581792.git.andre.glover@linux.intel.com> (raw)
In-Reply-To: <cover.1714581792.git.andre.glover@linux.intel.com>

Add the 'by_n' attribute to the acomp_req. The 'by_n' attribute can be
used a directive by acomp crypto algorithms for splitting compress and
decompress operations into "n" separate jobs.
 
Signed-off-by: Andre Glover <andre.glover@linux.intel.com>
---
 include/crypto/acompress.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/crypto/acompress.h b/include/crypto/acompress.h
index 2b73cef2f430..c687729e1966 100644
--- a/include/crypto/acompress.h
+++ b/include/crypto/acompress.h
@@ -25,6 +25,7 @@
  * @slen:	Size of the input buffer
  * @dlen:	Size of the output buffer and number of bytes produced
  * @flags:	Internal flags
+ * @by_n:	by_n setting used by acomp alg
  * @__ctx:	Start of private context data
  */
 struct acomp_req {
@@ -34,6 +35,7 @@ struct acomp_req {
 	unsigned int slen;
 	unsigned int dlen;
 	u32 flags;
+	u32 by_n;
 	void *__ctx[] CRYPTO_MINALIGN_ATTR;
 };
 
-- 
2.27.0



  parent reply	other threads:[~2024-05-01 21:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 21:46 [RFC PATCH 0/3] by_n compression and decompression with Intel IAA Andre Glover
2024-05-01 21:46 ` [RFC PATCH 1/3] crypto: Add pre_alloc and post_free callbacks for acomp algorithms Andre Glover
2024-05-01 21:46 ` Andre Glover [this message]
2024-09-16  6:16   ` [RFC PATCH 2/3] crypto: add by_n attribute to acomp_req Barry Song
2024-09-27 16:03     ` bala.seshasayee
2024-05-01 21:46 ` [RFC PATCH 3/3] crypto: Add deflate-canned-byN algorithm to IAA Andre Glover

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=8fe04e86f0907588d210885ac91965960f97f450.1714581792.git.andre.glover@linux.intel.com \
    --to=andre.glover@linux.intel.com \
    --cc=21cnbao@gmail.com \
    --cc=bala.seshasayee@intel.com \
    --cc=chengming.zhou@linux.dev \
    --cc=dave.jiang@intel.com \
    --cc=davem@davemloft.net \
    --cc=dmaengine@vger.kernel.org \
    --cc=fenghua.yu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=heath.caldwell@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=james.guilford@intel.com \
    --cc=kanchana.p.sridhar@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=nphamcs@gmail.com \
    --cc=ryan.roberts@arm.com \
    --cc=senozhatsky@chromium.org \
    --cc=tom.zanussi@linux.intel.com \
    --cc=vinodh.gopal@intel.com \
    --cc=wajdi.k.feghali@intel.com \
    --cc=yosryahmed@google.com \
    /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