From: Arjan van de Ven <arjanv@redhat.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>, linux-kernel@vger.kernel.org
Subject: Re: Stress testing 2.4.14-pre6
Date: Thu, 01 Nov 2001 17:29:27 +0000 [thread overview]
Message-ID: <3BE18677.556C9CDE@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0111010903280.11617-100000@penguin.transmeta.com> <3BE18402.9F958EDC@mandrakesoft.com>
Jeff Garzik wrote:
>
> Linus Torvalds wrote:
> > Anyway, I seriously doubt this explains any real-world bad behaviour: the
> > window for the interrupt hitting a half-way updated list is something like
> > two instructions long out of the whole memory freeing path. AND most
> > interrupts don't actually do any allocation.
>
> Network Rx interrupts do.... definitely not as frequent as IDE
> interrupts, but not infrequent.
Cerberus doesn't use networking in the tested setup iirc
next prev parent reply other threads:[~2001-11-01 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 21:57 Stress testing 2.4.14-pre6 Bob Matthews
2001-11-01 0:40 ` Alan Cox
2001-11-01 16:24 ` Linus Torvalds
2001-11-01 15:41 ` Marcelo Tosatti
2001-11-01 17:08 ` Linus Torvalds
2001-11-01 17:18 ` Jeff Garzik
2001-11-01 17:29 ` Arjan van de Ven [this message]
2001-11-01 18:15 ` Jens Axboe
2001-11-01 18:20 ` Jeff Garzik
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=3BE18677.556C9CDE@redhat.com \
--to=arjanv@redhat.com \
--cc=jgarzik@mandrakesoft.com \
--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 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.