All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom McNeal <tmcneal@mvista.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] stresstest.sh
Date: Mon, 19 Sep 2005 08:49:22 -0700	[thread overview]
Message-ID: <432EDE02.8090106@mvista.com> (raw)
In-Reply-To: <20050916151835.3bc8e5cc@dxpl.pdx.osdl.net>

Stephen Hemminger wrote:
> On Fri, 16 Sep 2005 14:43:42 -0700
> Tom McNeal <tmcneal@mvista.com> wrote:
> 
>>Hi -
>>
>>When running the stress tests, after a few hours, a panic occurs
>>due to a kernel page fault for address 0x0 while executing one
>>of the brctl commands.  We don't know which one, yet.  Has anyone
>>run across this?
>>
>>This is basically in the 2.4.17 kernel, with some of the security
>>fixes.
>>
>>Tom
> 
> 
> Some basics:
> 	* 2.4.17 is pretty old, can you at least try 2.4.30 or later.
>           Better yet, 2.6
> 	* Why are you doing bridge commands during the stress test?
> 	  it is pretty much a setup and forget it thing.
> 	* are you using SMP?  Locking in bridge code for 2.4 is pretty
> 	  weak and there are probably holes. I ended up reworking the whole
> 	  locking model of bridge code for 2.6 for speed and correctness.
> 

By 'bridge commands' I meant the brctl command, used by the stress
tests posted in the bridge-utils-1.0.6 test directory.  The tests
add and delete bridges while independently adding and deleting
interfaces to the supposedly existing bridge, in independent loops.
How real world is that?

I'm pretty sure it is SMP; are there fixes, like the ones you added
in 2.4.22 and 2.4.27, which are relevant?  I'm looking at trying to
patch 2.4.17 right now (I can't upgrade, but I can patch).  I do
seem some locking stuff that I'm going to look at now....

Thanks -

Tom
-- 
Tom McNeal
MontaVista Software
408-992-4459


  reply	other threads:[~2005-09-19 15:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-16 21:43 [Bridge] stresstest.sh Tom McNeal
2005-09-16 22:18 ` Stephen Hemminger
2005-09-19 15:49   ` Tom McNeal [this message]
2005-09-19 16:34     ` Stephen Hemminger
2005-09-21 16:37       ` Tom McNeal

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=432EDE02.8090106@mvista.com \
    --to=tmcneal@mvista.com \
    --cc=bridge@lists.osdl.org \
    --cc=shemminger@osdl.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.