From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Yosry Ahmed <yosry.ahmed@linux.dev>,
Eric Biggers <ebiggers@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: [RFC PATCH 7/7] mm: zswap: Use acomp virtual address interface
Date: Tue, 4 Mar 2025 17:33:05 +0900 [thread overview]
Message-ID: <vghra5lyaxc7zgzgqrewa5yxanziuh4d444w45ukt6dye3hhfg@ukgknqwyru35> (raw)
In-Reply-To: <Z8aZPcgzuaNR6N8L@gondor.apana.org.au>
On (25/03/04 14:10), Herbert Xu wrote:
[..]
> +static void zs_map_object_sg(struct zs_pool *pool, unsigned long handle,
> + enum zs_mapmode mm, struct scatterlist sg[2])
> +{
> + int handle_size = ZS_HANDLE_SIZE;
> + struct zspage *zspage;
> + struct zpdesc *zpdesc;
> + unsigned long obj, off;
> + unsigned int obj_idx;
> +
> + struct size_class *class;
> + struct zpdesc *zpdescs[2];
> +
> + /* It guarantees it can get zspage from handle safely */
> + read_lock(&pool->migrate_lock);
> + obj = handle_to_obj(handle);
> + obj_to_location(obj, &zpdesc, &obj_idx);
> + zspage = get_zspage(zpdesc);
> +
> + /*
> + * migration cannot move any zpages in this zspage. Here, class->lock
> + * is too heavy since callers would take some time until they calls
> + * zs_unmap_object API so delegate the locking from class to zspage
> + * which is smaller granularity.
> + */
> + migrate_read_lock(zspage);
> + read_unlock(&pool->migrate_lock);
> +
> + class = zspage_class(pool, zspage);
> + off = offset_in_page(class->size * obj_idx);
> +
> + if (unlikely(ZsHugePage(zspage)))
> + handle_size = 0;
> +
> + if (off + class->size <= PAGE_SIZE) {
> + /* this object is contained entirely within a page */
> + sg_init_table(sg, 1);
> + sg_set_page(sg, zpdesc_page(zpdesc), class->size - handle_size,
> + off + handle_size);
> + return;
> + }
> +
> + /* this object spans two pages */
> + zpdescs[0] = zpdesc;
> + zpdescs[1] = get_next_zpdesc(zpdesc);
> + BUG_ON(!zpdescs[1]);
> +
> + sg_init_table(sg, 2);
> + sg_set_page(sg, zpdesc_page(zpdescs[0]),
> + PAGE_SIZE - off - handle_size, off + handle_size);
> + sg_set_page(&sg[1], zpdesc_page(zpdescs[1]),
> + class->size - (PAGE_SIZE - off - handle_size), 0);
> +}
[..]
> static void zswap_decompress(struct zswap_entry *entry, struct folio *folio)
> {
> struct zpool *zpool = entry->pool->zpool;
> - struct scatterlist input, output;
> struct crypto_acomp_ctx *acomp_ctx;
> - u8 *src;
> + struct scatterlist input[2];
> + struct scatterlist output;
>
> acomp_ctx = acomp_ctx_get_cpu_lock(entry->pool);
> - src = zpool_map_handle(zpool, entry->handle, ZPOOL_MM_RO);
> - /*
> - * If zpool_map_handle is atomic, we cannot reliably utilize its mapped buffer
> - * to do crypto_acomp_decompress() which might sleep. In such cases, we must
> - * resort to copying the buffer to a temporary one.
> - * Meanwhile, zpool_map_handle() might return a non-linearly mapped buffer,
> - * such as a kmap address of high memory or even ever a vmap address.
> - * However, sg_init_one is only equipped to handle linearly mapped low memory.
> - * In such cases, we also must copy the buffer to a temporary and lowmem one.
> - */
> - if ((acomp_ctx->is_sleepable && !zpool_can_sleep_mapped(zpool)) ||
> - !virt_addr_valid(src)) {
> - memcpy(acomp_ctx->buffer, src, entry->length);
> - src = acomp_ctx->buffer;
> - zpool_unmap_handle(zpool, entry->handle);
> - }
> -
> - sg_init_one(&input, src, entry->length);
> + zpool_map_sg(zpool, entry->handle, ZPOOL_MM_RO, input);
> sg_init_table(&output, 1);
> sg_set_folio(&output, folio, PAGE_SIZE, 0);
> - acomp_request_set_params(acomp_ctx->req, &input, &output, entry->length, PAGE_SIZE);
> + acomp_request_set_params(acomp_ctx->req, input, &output, entry->length, PAGE_SIZE);
> BUG_ON(crypto_wait_req(crypto_acomp_decompress(acomp_ctx->req), &acomp_ctx->wait));
> BUG_ON(acomp_ctx->req->dlen != PAGE_SIZE);
And at some point you do memcpy() from SG list to a local buffer?
zsmalloc map() has a shortcut - for objects that fit one physical
page (that includes huge incompressible PAGE_SIZE-ed objects)
zsmalloc kmap the physical page in question and returns a pointer
to that mapping.
next prev parent reply other threads:[~2025-03-04 8:40 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 10:14 [PATCH 0/7] crypto: acomp - Add request chaining and virtual address support Herbert Xu
2025-02-27 10:14 ` [PATCH 1/7] crypto: iaa - Test the correct request flag Herbert Xu
2025-02-27 10:14 ` [PATCH 2/7] crypto: acomp - Remove acomp request flags Herbert Xu
2025-02-27 10:15 ` [PATCH 3/7] crypto: acomp - Add request chaining and virtual addresses Herbert Xu
2025-02-27 18:33 ` Eric Biggers
2025-02-27 10:15 ` [PATCH 4/7] crypto: testmgr - Remove NULL dst acomp tests Herbert Xu
2025-02-27 10:15 ` [PATCH 5/7] crypto: scomp - Remove support for non-trivial SG lists Herbert Xu
2025-02-27 10:15 ` [PATCH 6/7] crypto: scomp - Add chaining and virtual address support Herbert Xu
2025-02-27 10:15 ` [RFC PATCH 7/7] mm: zswap: Use acomp virtual address interface Herbert Xu
2025-02-27 18:11 ` Yosry Ahmed
2025-02-27 18:38 ` Eric Biggers
2025-02-27 21:43 ` Yosry Ahmed
2025-02-28 8:13 ` Herbert Xu
2025-02-28 9:54 ` Herbert Xu
2025-02-28 15:56 ` Yosry Ahmed
2025-03-01 6:36 ` Herbert Xu
2025-03-01 7:03 ` Herbert Xu
2025-03-03 20:17 ` Yosry Ahmed
2025-03-04 3:29 ` Herbert Xu
2025-03-04 4:30 ` Yosry Ahmed
2025-03-04 6:10 ` Herbert Xu
2025-03-04 8:33 ` Sergey Senozhatsky [this message]
2025-03-04 8:42 ` Herbert Xu
2025-03-04 8:45 ` Sergey Senozhatsky
2025-03-04 13:19 ` Sergey Senozhatsky
2025-03-04 20:47 ` Yosry Ahmed
2025-03-05 3:45 ` Herbert Xu
[not found] ` <Z8fssWOSw0kfggsM@google.com>
2025-03-05 7:41 ` Herbert Xu
2025-03-05 17:07 ` Nhat Pham
2025-03-06 2:48 ` Sergey Senozhatsky
2025-03-05 3:40 ` Herbert Xu
[not found] ` <Z8fsXZNgEbVkZrJP@google.com>
2025-03-05 7:46 ` Herbert Xu
2025-03-05 14:10 ` Herbert Xu
2025-03-05 16:25 ` Yosry Ahmed
2025-03-06 0:40 ` Herbert Xu
2025-03-06 16:58 ` Yosry Ahmed
2025-03-01 7:34 ` Herbert Xu
2025-03-01 7:38 ` Herbert Xu
2025-02-27 18:11 ` [PATCH 0/7] crypto: acomp - Add request chaining and virtual address support Yosry Ahmed
2025-02-28 9:02 ` Herbert Xu
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=vghra5lyaxc7zgzgqrewa5yxanziuh4d444w45ukt6dye3hhfg@ukgknqwyru35 \
--to=senozhatsky@chromium.org \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yosry.ahmed@linux.dev \
/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