From: Roberto Nibali <ratz@tac.ch>
To: Ion Badulescu <ionut@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <andrewm@uow.edu.au>
Subject: Re: Fix for Donald Becker's DP83815 network driver (v1.07)
Date: Fri, 20 Apr 2001 12:12:32 +0200 [thread overview]
Message-ID: <3AE00B90.ECF63D78@tac.ch> (raw)
In-Reply-To: <Pine.LNX.4.33.0104200227420.5165-100000@age.cs.columbia.edu>
Hi Ion,
> I think the UP-APIC support was added primarily to support the NMI oopser
> on UP systems. I might be wrong, though.
You're right, at least from the perspective of this patch:
http://www.csd.uu.se/~mikpe/linux/upapic/upapic-2.4.1
> You can safely disregard the "early initialization deferred" messages.
> They are essentially harmless.
Thanks for the info. I can sleep now :)
> As for the 16 eth ports limit, if you want to increase it, simply edit
> drivers/net/net_init.c and change the value of MAX_ETH_CARDS. This limit
> appears to also affect modules, so my earlier suggestion of using modules
> wouldn't have helped.
Thanks a lot. And sorry I don't know the kernel sources and documentations
good enough yet.
> If the only thing you need from your boxes is networking-related, than
> it's probably ok. Otherwise I'd wait a bit longer before putting 2.4 on
> production servers...
It is only network related (packetfiltering and load balancing with QoS)
and I like the improved mm. I've been testing 2.4 since its early days
and f.e. on the Intel L440GX+ boards it runs like hell, also with SMP.
Only the CPU numbering is incorrect if the kernel is SMP and you only
put in one processor. But I read somewhere that also this feature is
normal since it seems to be impossible to give the CPUs the correct
numbers because there is no defined order of initialization.
> Yeah, I guess I'll submit a patch to remove the experimental bit, after
> the current code changes are accepted..
Good. Yes, I saw the patches. I might try it out back here with a 2.4.x
kernel and 4 quadboards.
> You shouldn't need to do that, it's just wasted memory. The ethX_dev was
> used mostly to avoid probing for ISA cards, which is completely irrelevant
> when using PCI cards. As for the 4 quadboards limit, see above -- all you
> need to change is MAX_ETH_CARDS.
Will certainly do that. And thank you again for this information.
Best regards,
Roberto Nibali, ratz
--
mailto: `echo NrOatSz@tPacA.cMh | sed 's/[NOSPAM]//g'`
prev parent reply other threads:[~2001-04-20 10:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 15:58 Fix for Donald Becker's DP83815 network driver (v1.07) Steve Hill
2001-04-17 16:16 ` Roberto Nibali
2001-04-17 16:30 ` Steve Hill
2001-04-17 17:12 ` Roberto Nibali
2001-04-18 10:25 ` Ion Badulescu
2001-04-18 11:32 ` Steve Hill
2001-04-18 15:14 ` Tim Hockin
2001-04-18 20:33 ` Ion Badulescu
2001-04-18 20:40 ` Steve Hill
2001-04-19 10:54 ` Roberto Nibali
2001-04-19 13:06 ` Roberto Nibali
2001-04-20 5:48 ` Ion Badulescu
2001-04-20 6:30 ` Jeff Garzik
2001-04-20 7:09 ` Ion Badulescu
2001-04-20 7:31 ` Jeff Garzik
2001-04-20 9:49 ` Ion Badulescu
2001-04-20 9:57 ` Jeff Garzik
2001-04-20 10:05 ` Ion Badulescu
2001-04-20 16:10 ` Roberto Nibali
2001-04-20 16:19 ` Jeff Garzik
2001-04-20 16:50 ` Roberto Nibali
2001-04-20 19:27 ` Ion Badulescu
2001-04-20 9:03 ` Roberto Nibali
2001-04-20 9:42 ` Ion Badulescu
2001-04-20 10:12 ` Roberto Nibali [this message]
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=3AE00B90.ECF63D78@tac.ch \
--to=ratz@tac.ch \
--cc=andrewm@uow.edu.au \
--cc=ionut@cs.columbia.edu \
--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 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.