[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200709084040.cf3jzkndiaefky4r@linutronix.de>
Date: Thu, 9 Jul 2020 10:40:40 +0200
From: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To: "Song Bao Hua (Barry Song)" <song.bao.hua@...ilicon.com>
Cc: "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>,
"davem@...emloft.net" <davem@...emloft.net>,
"linux-crypto@...r.kernel.org" <linux-crypto@...r.kernel.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linuxarm <linuxarm@...wei.com>,
"Luis Claudio R . Goncalves" <lgoncalv@...hat.com>,
Mahipal Challa <mahipalreddy2006@...il.com>,
Seth Jennings <sjenning@...hat.com>,
Dan Streetman <ddstreet@...e.org>,
Vitaly Wool <vitaly.wool@...sulko.com>,
"Wangzhou (B)" <wangzhou1@...ilicon.com>,
Colin Ian King <colin.king@...onical.com>
Subject: Re: [PATCH v4] mm/zswap: move to use crypto_acomp API for hardware
acceleration
On 2020-07-09 07:55:22 [+0000], Song Bao Hua (Barry Song) wrote:
> Hello Sebastian, thanks for your reply and careful review.
Hi,
> I don't think we can simply "forward the result to the caller and let him decide".
> Would you like to present some pseudo code?
I provided just some pseudo code to illustrate an example how the async
interface should look like (more or less). The essential part is where
you allow to feed multiple requests without blocking.
I went up the call-chain and found one potential user which seem to have
a list of pages which are processed. This looked like a nice example. I
haven't looked at the details.
I have no opinion whether or not it makes sense to switch to the async
interface in a sync way.
> Thanks
> Barry
Sebastian
Powered by blists - more mailing lists