From: "David S. Miller" <davem@redhat.com>
To: george@mvista.com
Cc: rml@tech9.net, kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Replace timer_bh with tasklet
Date: Thu, 20 Jun 2002 18:03:58 -0700 (PDT) [thread overview]
Message-ID: <20020620.180358.33292945.davem@redhat.com> (raw)
In-Reply-To: <3D126B28.16C88E2B@mvista.com>
From: george anzinger <george@mvista.com>
Date: Thu, 20 Jun 2002 16:54:16 -0700
Is the only network issue? Is it possible that the network code
uses bh_locking to protect against timers? Moveing timers to
softirqs would invalidate this sort of protection. Is this an
issue?
It is the whole issue. We have to stop all timers while we run the
non-SMP safe protocol code.
next prev parent reply other threads:[~2002-06-21 1:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 3:45 [PATCH] Replace timer_bh with tasklet george anzinger
2002-06-18 4:06 ` Linus Torvalds
2002-06-18 18:07 ` george anzinger
2002-06-18 22:46 ` Richard Zidlicky
2002-06-18 23:17 ` george anzinger
2002-06-19 11:43 ` Richard Zidlicky
2002-06-18 4:15 ` David S. Miller
2002-06-18 17:01 ` george anzinger
2002-06-18 17:12 ` Matthew Wilcox
2002-06-18 18:14 ` george anzinger
2002-06-18 5:16 ` kuznet
2002-06-18 18:19 ` george anzinger
2002-06-18 18:29 ` kuznet
2002-06-20 0:39 ` george anzinger
2002-06-20 1:34 ` David S. Miller
2002-06-20 1:53 ` Robert Love
2002-06-20 1:55 ` David S. Miller
2002-06-20 2:05 ` Robert Love
2002-06-20 2:01 ` David S. Miller
2002-06-20 2:15 ` Robert Love
2002-06-20 2:23 ` David S. Miller
2002-06-20 23:54 ` george anzinger
2002-06-21 1:03 ` David S. Miller [this message]
2002-06-21 14:04 ` george anzinger
2002-06-21 14:08 ` David S. Miller
2002-06-20 8:11 ` Russell King
2002-06-20 8:09 ` David S. Miller
2002-06-20 8:16 ` Russell King
2002-06-20 8:13 ` Russell King
2002-06-20 14:33 ` 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=20020620.180358.33292945.davem@redhat.com \
--to=davem@redhat.com \
--cc=george@mvista.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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