DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=hbWzC72Ju50H9VxXGl2oDSnA/ENNK6jjH6IYV6By/RnEqsiQXCFMl90EH+Wmr+/9wQnX5UTP4lCSiLdWBN1z8rAoYzGGED/DoBofbPGpsHjpXuGmWnxKInCY/3i4ytH/9/qkBeQy6WJmloYEmVWuM+7mvwKMoh9b0VTzg5MyM98=
Message-ID: <20f65d530709250103s556231a5vbb3741e11197df6c@mail.gmail.com>
Date: Tue, 25 Sep 2007 20:03:27 +1200
From: "Keith Chew" <keith.chew@gmail.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: oom on wireless network saturation
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 855
Lines: 22

Hi

We are stress testing the wireless network driver on our linux system.
We use ping flood to saturate the network, and within 24 hours, we
managed to crash the driver.

This was a good test, as it hightlighted a timer problem in the
driver. After fixing that, we are now getting out of memory errors.
The OOM killer starts to kick in and the system freezes.

Can someone advise at a high level, what should the network driver do
in such a scenario? Essentially, the wireless packets get queued up in
the driver and eventually it just breaks. What is the correct way to
handle this gracefully?

Regards
Keith
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/