From: Andrea Arcangeli <andrea@suse.de>
To: "David S. Miller" <davem@redhat.com>
Cc: Paul Mackerras <paulus@samba.org>,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Ingo Molnar <mingo@elte.hu>,
kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: softirq in pre3 and all linux ports
Date: Wed, 20 Jun 2001 06:07:53 +0200 [thread overview]
Message-ID: <20010620060753.B849@athlon.random> (raw)
In-Reply-To: <20010619210312.Z11631@athlon.random> <15152.6527.366544.713462@cargo.ozlabs.ibm.com> <20010620055413.A849@athlon.random> <15152.8152.177595.177731@pizda.ninka.net>
In-Reply-To: <15152.8152.177595.177731@pizda.ninka.net>; from davem@redhat.com on Tue, Jun 19, 2001 at 09:00:24PM -0700
On Tue, Jun 19, 2001 at 09:00:24PM -0700, David S. Miller wrote:
>
> Andrea Arcangeli writes:
> > I don't have gigabit ethernet so I cannot flood my boxes to death.
> > But I think it's real, and a softirq marking itself runnable again is
> > another case to handle without live lockups or starvation.
>
> I think (still) that you're just moving the problem around and
> not actually changing anything.
something will defintely to change radically if the softirq marks itself
runnable again. but this to me sounds similar to the other one (irq
flood that basically left the softirq pending every time you check it).
Andrea
next prev parent reply other threads:[~2001-06-20 4:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-19 19:03 softirq in pre3 and all linux ports Andrea Arcangeli
2001-06-20 3:33 ` Paul Mackerras
2001-06-20 3:54 ` Andrea Arcangeli
2001-06-20 4:00 ` David S. Miller
2001-06-20 4:07 ` Andrea Arcangeli [this message]
2001-06-20 18:06 ` kuznet
2001-06-20 22:10 ` David S. Miller
2001-06-20 23:16 ` Andrea Arcangeli
2001-06-21 16:58 ` kuznet
2001-06-20 12:18 ` Paul Mackerras
2001-06-20 12:52 ` Andrea Arcangeli
2001-06-20 18:16 ` kuznet
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=20010620060753.B849@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox