Linux cryptographic layer development
 help / color / mirror / Atom feed
From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: 罗鹏 <wuhanluop@163.com>
Cc: herbert@gondor.apana.org.au, salvatore.benedetto@intel.com,
	davem@davemloft.net, qat-linux@intel.com,
	linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: A bug of QAT?
Date: Thu, 24 Mar 2022 12:36:10 +0000	[thread overview]
Message-ID: <YjxluoHM+FHWtaR0@silpixa00400314> (raw)
In-Reply-To: <7d3b3812.10d5.17fb9964788.Coremail.wuhanluop@163.com>

On Thu, Mar 24, 2022 at 09:41:48AM +0800, 罗鹏 wrote:
...
> But the request is not cached. And there is no time to rehandle the request
> later.
> 
> This may cause a problem?
Yes, this is a known problem.
I sent an RFC with a fix to the ML a few weeks ago:
https://patchwork.kernel.org/project/linux-crypto/patch/20220303180036.13475-3-giovanni.cabiddu@intel.com/

I'm going to send a final set early next week.

Regards,

-- 
Giovanni

           reply	other threads:[~2022-03-24 12:36 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <7d3b3812.10d5.17fb9964788.Coremail.wuhanluop@163.com>]

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=YjxluoHM+FHWtaR0@silpixa00400314 \
    --to=giovanni.cabiddu@intel.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qat-linux@intel.com \
    --cc=salvatore.benedetto@intel.com \
    --cc=wuhanluop@163.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