From: Georg Nikodym <georgn@somanetworks.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.4.20-rmap15b
Date: Tue, 17 Dec 2002 16:54:56 -0500 [thread overview]
Message-ID: <200212172154.gBHLsu5E011391@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.50L.0212171948400.26879-100000@imladris.surriel.com>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On Tue, 17 Dec 2002 19:50:04 -0200 (BRST)
Rik van Riel <riel@conectiva.com.br> wrote:
> On Mon, 16 Dec 2002, Georg Nikodym wrote:
>
> > Incidentally, a colleague claimed to have seem this behaviour on a
> > non-rmap 2.4.20.
>
> > 1. Known behaviour?
> > 2. Is there any data that I should be collecting that people are
> > interested in?
> > 3. Or should I just go back to 2.4.19-rmap14b (which did not trouble
> > me
> > in this way)?
>
> The suspect is the disk elevator, which isn't scheduling requests
> in a way to cause lower read latency, but is optimised more for
> throughput. This results in some pauses.
>
> I'll need to look into it.
I discovered after sending the above:
Dec 16 15:08:04 keller kernel: ieee1394: sbp2: sbp2util_allocate_request_packet
- no packets available!
Dec 16 15:08:04 keller kernel: ieee1394: sbp2: sbp2util_allocate_write_request_p
acket failed
Dec 16 15:08:34 keller kernel: ieee1394: sbp2: aborting sbp2 command
These messages correspond with the pauses... However, the ieee1394 code
has not changed in some time (as in many months).
-g
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-12-17 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 1:51 [PATCH] 2.4.20-rmap15b Rik van Riel
2002-12-13 1:51 ` Rik van Riel
2002-12-13 9:25 ` Eyal Lebedinsky
2002-12-13 10:55 ` [PATCH] 2.4.20-rmap15b - compile failure Eyal Lebedinsky
2002-12-13 11:30 ` Rik van Riel
2002-12-16 16:10 ` [PATCH] 2.4.20-rmap15b Georg Nikodym
2002-12-17 21:50 ` Rik van Riel
2002-12-17 21:50 ` Rik van Riel
2002-12-17 21:54 ` Georg Nikodym [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=200212172154.gBHLsu5E011391@localhost.localdomain \
--to=georgn@somanetworks.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
/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.