All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] [1/4] /dev/random: Fix latency in rekeying sequence number
Date: Fri, 20 Aug 2004 01:10:26 -0400	[thread overview]
Message-ID: <1092978626.10063.15.camel@krustophenia.net> (raw)
In-Reply-To: <E1By1Sh-0001TJ-1U@thunk.org>

On Fri, 2004-08-20 at 00:57, Theodore Ts'o wrote:
> Based on reports from Ingo's Latency Tracer that the TCP sequence number
> rekey code is causing latency problems, I've moved the sequence number
> rekey to be done out of a workqueue.
> 

This patch does not actually fix the problem, as 3-700usecs is still
spent in the spinlocked region, this just causes it to be done out of a
workqueue.  It reduces the incidence of problems, but for latency
sensitive applications the worst-case is the important one.

Lee


  reply	other threads:[~2004-08-20  5:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-20  4:57 [PATCH] [1/4] /dev/random: Fix latency in rekeying sequence number Theodore Ts'o
2004-08-20  5:10 ` Lee Revell [this message]
2004-08-22 21:31   ` Jens Maurer

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=1092978626.10063.15.camel@krustophenia.net \
    --to=rlrevell@joe-job.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.