From: Herbert Xu <herbert@gondor.apana.org.au>
To: Ignat Korchagin <ignat@cloudflare.com>
Cc: Mike Snitzer <snitzer@redhat.com>,
Mikulas Patocka <mpatocka@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
agk@redhat.com, dm-devel@redhat.com, dm-crypt@saout.de,
linux-kernel <linux-kernel@vger.kernel.org>,
kernel-team <kernel-team@cloudflare.com>
Subject: Re: [RFC PATCH 0/1] dm-crypt excessive overhead
Date: Wed, 24 Jun 2020 10:23:01 +1000 [thread overview]
Message-ID: <20200624002301.GB12716@gondor.apana.org.au> (raw)
In-Reply-To: <CALrw=nEjCdg8BuTFT81+tCDtuxgwy05FKZAdvk3oq+pauW0nDA@mail.gmail.com>
On Tue, Jun 23, 2020 at 05:24:39PM +0100, Ignat Korchagin wrote:
>
> I may be misunderstanding the terminology, but tasklets execute in
> soft IRQ, don't they? What we care about is to execute the decryption
> as fast as possible, but we can't do it in a hard IRQ context (that
> is, the interrupt context where other interrupts are disabled). As far
> as I understand, tasklets are executed right after the hard IRQ
> context, but with interrupts enabled - which is the first safe-ish
> place to do more lengthy processing without the risk of missing an
> interrupt.
Yes you are absolutely right. In general high-performance work
should be carried out in softirq context. That's how the networking
stack works for example.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2020-06-24 0:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-19 16:41 [RFC PATCH 0/1] dm-crypt excessive overhead Ignat Korchagin
2020-06-19 16:41 ` [RFC PATCH 1/1] Add DM_CRYPT_FORCE_INLINE flag to dm-crypt target Ignat Korchagin
2020-06-24 5:04 ` [dm-crypt] " Eric Biggers
2020-06-24 5:21 ` [dm-devel] " Damien Le Moal
2020-06-24 5:27 ` Eric Biggers
2020-06-24 6:46 ` Damien Le Moal
2020-06-24 7:24 ` Damien Le Moal
2020-06-24 7:49 ` Damien Le Moal
2020-06-24 8:24 ` Ignat Korchagin
2020-06-24 16:24 ` Eric Biggers
2020-06-24 17:00 ` Ignat Korchagin
2020-06-24 5:12 ` [dm-devel] " Damien Le Moal
2020-06-19 16:55 ` [RFC PATCH 0/1] dm-crypt excessive overhead Mike Snitzer
2020-06-19 18:39 ` Mikulas Patocka
2020-06-19 19:44 ` Ignat Korchagin
2020-06-20 1:23 ` Herbert Xu
2020-06-20 19:36 ` Mikulas Patocka
2020-06-20 21:02 ` Ignat Korchagin
2020-06-23 15:33 ` Mike Snitzer
2020-06-23 16:24 ` Ignat Korchagin
2020-06-24 0:23 ` Herbert Xu [this message]
2020-06-22 0:45 ` [dm-devel] " Damien Le Moal
2020-06-22 7:55 ` Ignat Korchagin
2020-06-22 8:08 ` Damien Le Moal
2020-06-23 15:01 ` Mike Snitzer
2020-06-23 15:07 ` Ignat Korchagin
2020-06-23 15:22 ` Mike Snitzer
2020-06-24 4:54 ` [dm-devel] " Damien Le Moal
2020-06-24 5:22 ` Mike Snitzer
2020-06-24 8:02 ` Ignat Korchagin
2020-06-24 4:28 ` Damien Le Moal
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=20200624002301.GB12716@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=agk@redhat.com \
--cc=davem@davemloft.net \
--cc=dm-crypt@saout.de \
--cc=dm-devel@redhat.com \
--cc=ignat@cloudflare.com \
--cc=kernel-team@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@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;
as well as URLs for NNTP newsgroup(s).