From: "Manfred Spraul" <manfred@colorfullife.com>
To: <Imran.Patel@nokia.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: skb allocation problems (More Brain damage!)
Date: Wed, 11 Apr 2001 22:02:00 +0200 [thread overview]
Message-ID: <001801c0c2c2$489f3050$5517fea9@local> (raw)
> it is very hard to imagine the scenario which can lead to this...
> I will try your suggestion..
Perhaps a problem with the csum assembler implementations? Which cpu
type do you optimize for, and which cpu is installed?
Btw, are you overclocking anything?
--
Manfred
next reply other threads:[~2001-04-11 20:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-11 20:02 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-11 19:02 skb allocation problems (More Brain damage!) Imran.Patel
2001-04-11 18:22 Imran.Patel
2001-04-11 17:24 Imran.Patel
2001-04-11 17:15 Imran.Patel
2001-04-11 17:20 ` Dave Airlie
2001-04-11 17:47 ` Bart Trojanowski
2001-04-11 18:25 ` Andi Kleen
2001-04-11 18:28 ` Andi Kleen
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='001801c0c2c2$489f3050$5517fea9@local' \
--to=manfred@colorfullife.com \
--cc=Imran.Patel@nokia.com \
--cc=linux-kernel@vger.kernel.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 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).