From: "Chris Friesen" <cfriesen@nortel.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: posible latency issues in seq_read
Date: Fri, 20 Jul 2007 16:39:24 -0600 [thread overview]
Message-ID: <46A1399C.8010405@nortel.com> (raw)
In-Reply-To: <75b66ecd0707201518j45ef8bb7q7e48462ffbbc9c58@mail.gmail.com>
Lee Revell wrote:
> On 7/20/07, Chris Friesen <cfriesen@nortel.com> wrote:
>> We've run into an issue (on 2.6.10) where calling "lsof" triggers lost
>> packets on our server. Preempt is disabled, and NAPI is enabled.
> Can you reproduce with a recent kernel? Lots of latency issues have
> been fixed since then.
Unfortunately I have to fix it on this version (the bug was found on
shipped product), so if there was a difference I'd have to isolate the
changes and backport them. Also, I can't run the software that triggers
the problem on a newer kernel as it has dependencies on various patches
that are not in mainline.
Basically what I'd like to know is whether calling schedule() in
seq_read() is safe or whether it would break assumptions made by
seq_file users.
Chris
next prev parent reply other threads:[~2007-07-20 22:39 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 [this message]
2007-07-21 3:46 ` Eric Dumazet
2007-07-23 17:45 ` Chris Friesen
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=46A1399C.8010405@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@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.