From: jamal <hadi@cyberus.ca>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: Patrick McHardy <kaber@trash.net>, Matt Mackall <mpm@selenic.com>,
Mark Broadbent <markb@wetlettuce.com>,
linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Lockup with 2.6.9-ac15 related to netconsole
Date: 22 Dec 2004 08:33:15 -0500 [thread overview]
Message-ID: <1103722395.1090.77.camel@jzny.localdomain> (raw)
In-Reply-To: <20041222123940.GA4241@electric-eye.fr.zoreil.com>
On Wed, 2004-12-22 at 07:39, Francois Romieu wrote:
> If I am not mistaken, a failure on spin_trylock + the test on
> xmit_lock_owner imply that it is safe to directly handle the
> queue. It means that qdisc_run() has been interrupted on the
> current cpu and the other paths seem fine as well. Counter-example
> is welcome (no joke).
Think more than 2 processors ;->
cheers,
jamal
next prev parent reply other threads:[~2004-12-22 13:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 16:20 Mark Broadbent
2004-12-16 21:10 ` Matt Mackall
2004-12-17 9:10 ` Mark Broadbent
2004-12-17 21:57 ` Matt Mackall
2004-12-17 23:35 ` Francois Romieu
2004-12-18 13:25 ` Mark Broadbent
2004-12-20 9:42 ` Mark Broadbent
2004-12-20 21:14 ` Matt Mackall
2004-12-21 0:22 ` Francois Romieu
2004-12-21 0:55 ` Matt Mackall
2004-12-21 10:23 ` Mark Broadbent
2004-12-21 12:37 ` Francois Romieu
2004-12-21 13:29 ` Mark Broadbent
2004-12-21 20:48 ` Francois Romieu
2004-12-21 21:27 ` Matt Mackall
2004-12-21 22:58 ` Francois Romieu
2004-12-22 9:34 ` Patrick McHardy
2004-12-22 10:54 ` Patrick McHardy
2004-12-22 12:39 ` Francois Romieu
2004-12-22 13:33 ` jamal [this message]
2004-12-22 14:57 ` Patrick McHardy
2004-12-22 17:18 ` Matt Mackall
2004-12-25 11:26 ` Wish you all a Merry Christmas Pranav
2004-12-25 11:30 ` Jan Engelhardt
2004-12-28 13:45 ` Lockup with 2.6.9-ac15 related to netconsole jamal
2004-12-22 14:37 ` Mark Broadbent
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=1103722395.1090.77.camel@jzny.localdomain \
--to=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=markb@wetlettuce.com \
--cc=mpm@selenic.com \
--cc=netdev@oss.sgi.com \
--cc=romieu@fr.zoreil.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
all inboxes | Powered by JetHome®