From: Pekka Pietikainen <pp@ee.oulu.fi>
To: Pavel Machek <pavel@suse.cz>
Cc: "David S. Miller" <davem@redhat.com>,
netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Dealing with buggy hardware (was: b44 and 4g4g)
Date: Thu, 10 Jun 2004 23:34:42 +0300 [thread overview]
Message-ID: <20040610203442.GA27762@ee.oulu.fi> (raw)
In-Reply-To: <20040610200504.GG4507@openzaurus.ucw.cz>
On Thu, Jun 10, 2004 at 10:05:04PM +0200, Pavel Machek wrote:
> This should hit machines with 2GB ram too, right?
> Is it possible to find if it hits me? I get hard lockups on
> 2GB machine with b44, but they take ~5min.. few hours to
> reproduce...
>
> It seems to me like this should hit very quickly.
> --
> 64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
>
Yikes!
With the 4:4 VM split it definately is instantaneous with > 1GB of memory, I
triggered it with 1.25G myself and never noticed anything wrong with just
1GB (allocation starts from the top it seems). With the standard 1:3 split I
don't think anything > 1GB ever gets used for skbuffs, but maybe there
are circumstances where this can happen?
(Or the issue isn't fully understood yet, figuring out what breaks and what
doesn't was basically just trial and error :-/ )
next prev parent reply other threads:[~2004-06-10 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-31 20:21 b44 and 4g4g Pekka Pietikainen
2004-06-05 20:06 ` Dealing with buggy hardware (was: b44 and 4g4g) Pekka Pietikainen
2004-06-05 20:19 ` David S. Miller
2004-06-09 12:29 ` Pekka Pietikainen
2004-06-10 20:05 ` Pavel Machek
2004-06-10 20:34 ` Pekka Pietikainen [this message]
2004-06-10 21:12 ` Pavel Machek
2004-06-11 6:17 ` Pekka Pietikainen
2004-06-11 9:45 ` Pavel Machek
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=20040610203442.GA27762@ee.oulu.fi \
--to=pp@ee.oulu.fi \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pavel@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).