From: Dan Streetman <ddstreet@ieee.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Mahipal Reddy <mahipalreddy2006@gmail.com>,
Mahipal Challa <Mahipal.Challa@cavium.com>,
Seth Jennings <sjenning@redhat.com>,
Linux-MM <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
pathreya@cavium.com, Vishnu Nair <Vishnu.Nair@cavium.com>
Subject: Re: [PATCH v2 1/1] mm: zswap - Add crypto acomp/scomp framework support
Date: Thu, 16 Mar 2017 14:20:56 -0400 [thread overview]
Message-ID: <CALZtONAjUCLceJMGQ5OD+vT3CqzywgU2JC5L2KWhJpA3nxng7w@mail.gmail.com> (raw)
In-Reply-To: <20170316163331.GA13997@gondor.apana.org.au>
On Thu, Mar 16, 2017 at 12:33 PM, Herbert Xu
<herbert@gondor.apana.org.au> wrote:
> On Wed, Mar 08, 2017 at 12:38:40PM -0500, Dan Streetman wrote:
>>
>>
>> setting the ASYNC bit makes it synchronous? that seems backwards...?
>
> You set the ASYNC bit in the mask and leave it clear in the type.
> That way only algorithms with the ASYNC bit off will match.
aha, ok i get it now.
>> zswap gets the fun of being the first crypto compression consumer to
>> switch to the new api? ;-)
>
> BTW I think we should hold off on converting zswap for now.
ok that sounds good, we can wait. Thanks!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-03-16 18:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 16:05 [PATCH v2 0/1] mm: zswap - crypto acomp/scomp support Mahipal Challa
2017-02-24 16:05 ` [PATCH v2 1/1] mm: zswap - Add crypto acomp/scomp framework support Mahipal Challa
2017-02-24 22:21 ` Dan Streetman
2017-02-27 14:40 ` Mahipal Reddy
2017-03-08 17:38 ` Dan Streetman
2017-03-09 9:39 ` Herbert Xu
2017-03-16 15:54 ` Dan Streetman
2017-03-16 16:17 ` Herbert Xu
2017-03-16 16:33 ` Herbert Xu
2017-03-16 18:20 ` Dan Streetman [this message]
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=CALZtONAjUCLceJMGQ5OD+vT3CqzywgU2JC5L2KWhJpA3nxng7w@mail.gmail.com \
--to=ddstreet@ieee.org \
--cc=Mahipal.Challa@cavium.com \
--cc=Vishnu.Nair@cavium.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mahipalreddy2006@gmail.com \
--cc=pathreya@cavium.com \
--cc=sjenning@redhat.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