All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Lee Revell <rlrevell@joe-job.com>,
	linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: posible latency issues in seq_read
Date: Mon, 23 Jul 2007 11:45:46 -0600	[thread overview]
Message-ID: <46A4E94A.3030301@nortel.com> (raw)
In-Reply-To: <46A181A5.5010203@cosmosbay.com>

Eric Dumazet wrote:

> The problem is in established_get_next() and established_get_first() not 
> allowing softirq processing, while scanning a possibly huge hash table, 
> even if few sockets are hashed in.
> 
> As cond_resched_softirq() was added in linux-2.6.11, you probably *need* 
> to check the diffs between linux-2.6.10 & linux-2.6.11

Thanks for the pointers to the likely culprits.

Chris

      reply	other threads:[~2007-07-23 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-20 21:15 posible latency issues in seq_read Chris Friesen
2007-07-20 22:18 ` Lee Revell
2007-07-20 22:39   ` Chris Friesen
2007-07-21  3:46     ` Eric Dumazet
2007-07-23 17:45       ` Chris Friesen [this message]

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=46A4E94A.3030301@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=dada1@cosmosbay.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@vger.kernel.org \
    --cc=rlrevell@joe-job.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 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.