public inbox for linux-crypto@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-crypto@vger.kernel.org
Subject: Re: [PATCH 13/29] crypto: scatterwalk - add new functions for iterating through data
Date: Mon, 23 Dec 2024 11:53:41 -0800	[thread overview]
Message-ID: <20241223195341.GC2032@quark.localdomain> (raw)
In-Reply-To: <Z2amIuU1sLDWBsSh@gondor.apana.org.au>

On Sat, Dec 21, 2024 at 07:27:30PM +0800, Herbert Xu wrote:
> Eric Biggers <ebiggers@kernel.org> wrote:
> >
> > +       if (ARCH_IMPLEMENTS_FLUSH_DCACHE_PAGE)
> > +               flush_dcache_page(scatterwalk_page(walk));
> 
> Does the if statement do anything? If so please add a comment
> about what it does because it's not obvious.
> 

Yes, since even though flush_dcache_page() is a no-op when
!ARCH_IMPLEMENTS_FLUSH_DCACHE_PAGE, scatterwalk_page() still calls sg_page()
which calls BUG_ON() when CONFIG_DEBUG_SG=y.  That can't be optimized out.  Note
that despite ostensibly being a debug option, CONFIG_DEBUG_SG=y is often used in
production kernels.  Also, in patch 29 this changes into a loop that may flush
multiple pages, and which makes it harder to show that it would get optimized
out even with CONFIG_DEBUG_SG=n; e.g., the compiler would have to prove that the
loop is finite.  I will add a comment to this patch and update it in patch 29.

- Eric

  reply	other threads:[~2024-12-23 19:53 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-21  9:10 [PATCH 00/29] crypto: scatterlist handling improvements Eric Biggers
2024-12-21  9:10 ` [PATCH 01/29] crypto: skcipher - document skcipher_walk_done() and rename some vars Eric Biggers
2024-12-21  9:10 ` [PATCH 02/29] crypto: skcipher - remove unnecessary page alignment of bounce buffer Eric Biggers
2024-12-21  9:10 ` [PATCH 03/29] crypto: skcipher - remove redundant clamping to page size Eric Biggers
2024-12-21  9:10 ` [PATCH 04/29] crypto: skcipher - remove redundant check for SKCIPHER_WALK_SLOW Eric Biggers
2024-12-21  9:10 ` [PATCH 05/29] crypto: skcipher - fold skcipher_walk_skcipher() into skcipher_walk_virt() Eric Biggers
2024-12-21  9:10 ` [PATCH 06/29] crypto: skcipher - clean up initialization of skcipher_walk::flags Eric Biggers
2024-12-21  9:10 ` [PATCH 07/29] crypto: skcipher - optimize initializing skcipher_walk fields Eric Biggers
2024-12-21 11:16   ` Herbert Xu
2024-12-29 22:10     ` Eric Biggers
2025-01-02  1:03       ` Herbert Xu
2024-12-21  9:10 ` [PATCH 08/29] crypto: skcipher - call cond_resched() directly Eric Biggers
2024-12-21  9:10 ` [PATCH 09/29] crypto: omap - switch from scatter_walk to plain offset Eric Biggers
2024-12-21  9:10 ` [PATCH 10/29] crypto: powerpc/p10-aes-gcm - simplify handling of linear associated data Eric Biggers
2024-12-21  9:10 ` [PATCH 11/29] crypto: scatterwalk - move to next sg entry just in time Eric Biggers
2024-12-21  9:10 ` [PATCH 12/29] crypto: scatterwalk - add new functions for skipping data Eric Biggers
2024-12-21  9:10 ` [PATCH 13/29] crypto: scatterwalk - add new functions for iterating through data Eric Biggers
2024-12-21 11:27   ` Herbert Xu
2024-12-23 19:53     ` Eric Biggers [this message]
2024-12-21  9:10 ` [PATCH 14/29] crypto: scatterwalk - add new functions for copying data Eric Biggers
2024-12-21  9:10 ` [PATCH 15/29] crypto: skcipher - use scatterwalk_start_at_pos() Eric Biggers
2024-12-21  9:10 ` [PATCH 16/29] crypto: aegis - use the new scatterwalk functions Eric Biggers
2024-12-21  9:10 ` [PATCH 17/29] crypto: arm/ghash " Eric Biggers
2024-12-21  9:10 ` [PATCH 18/29] crypto: arm64 " Eric Biggers
2024-12-21  9:10 ` [PATCH 19/29] crypto: keywrap " Eric Biggers
2024-12-21  9:10 ` [PATCH 20/29] crypto: nx " Eric Biggers
2024-12-21  9:10 ` [PATCH 21/29] crypto: s390/aes-gcm " Eric Biggers
2024-12-21  9:10 ` [PATCH 22/29] crypto: s5p-sss " Eric Biggers
2024-12-21  9:10 ` [PATCH 23/29] crypto: stm32 " Eric Biggers
2024-12-21  9:10 ` [PATCH 24/29] crypto: x86/aes-gcm " Eric Biggers
2024-12-21  9:10 ` [PATCH 25/29] crypto: x86/aegis " Eric Biggers
2024-12-21  9:10 ` [PATCH 26/29] net/tls: " Eric Biggers
2024-12-23 15:48   ` Jakub Kicinski
2024-12-23 19:42     ` Eric Biggers
2024-12-23 20:44       ` Jakub Kicinski
2024-12-29 23:58         ` Eric Biggers
2024-12-21  9:10 ` [PATCH 27/29] crypto: skcipher - " Eric Biggers
2024-12-21  9:10 ` [PATCH 28/29] crypto: scatterwalk - remove obsolete functions Eric Biggers
2024-12-21  9:10 ` [PATCH 29/29] crypto: scatterwalk - don't split at page boundaries when !HIGHMEM Eric Biggers

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=20241223195341.GC2032@quark.localdomain \
    --to=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    /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