mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	davem@davemloft.net, jmorris@redhat.com
Subject: Re: [CRYPTO]: Only reschedule if !in_atomic()
Date: Mon, 23 May 2005 19:31:16 -0700	[thread overview]
Message-ID: <20050523193116.62844826.akpm@osdl.org> (raw)
In-Reply-To: <20050524022106.GA29081@gondor.apana.org.au>

Herbert Xu <herbert@gondor.apana.org.au> wrote:
>
> Perhaps we should code this into the crypto API instead? For instance,
>  we can have a tfm flag that says whether we can sleep or not.

Are you sure it's actually needed? Have significant scheduling latencies
actually been observed?

Bear in mind that anyone who cares a lot about latency will be running
CONFIG_PREEMPT kernels, in which case the whole thing is redundant anyway. 
I generally take the position that if we're going to put a scheduling point
into a non-premept kernel then it'd better be for a pretty bad latency
point - more than 10 milliseconds, say.


  reply	other threads:[~2005-05-24  2:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200505232300.j4NN07lE012726@hera.kernel.org>
2005-05-23 23:28 ` Andrew Morton
2005-05-23 23:58   ` Benjamin Herrenschmidt
2005-05-24  0:24     ` Andrew Morton
2005-05-24  2:21   ` Herbert Xu
2005-05-24  2:31     ` Andrew Morton [this message]
2005-05-24  2:43       ` Herbert Xu
2005-05-24  3:20         ` James Morris
2005-05-24  3:50           ` Herbert Xu
2005-05-24 13:32       ` Bill Davidsen
     [not found]     ` <20050523.193612.08320356.davem@davemloft.net>
2005-05-24  3:47       ` Herbert Xu
2005-05-24  6:40 ` Arjan van de Ven

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=20050523193116.62844826.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jmorris@redhat.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®