From: Chris Friesen <cfriesen@nortelnetworks.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Chris Dukes <pakrat@www.uk.linux.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jgarzik@pobox.com>, Robin Holt <holt@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com
Subject: Re: Make ipconfig.c work as a loadable module.
Date: Fri, 07 Mar 2003 17:00:15 -0500 [thread overview]
Message-ID: <3E69166F.9080604@nortelnetworks.com> (raw)
In-Reply-To: 20030307214749.GA20188@holomorphy.com
William Lee Irwin III wrote:
> On Fri, Mar 07, 2003 at 09:42:35AM +0000, Russell King wrote:
>
>>That's getting on for 2MB vs:
>> 2620 2012 0 4632 1218 fs/nfs/nfsroot.o
>> 8016 380 80 8476 211c net/ipv4/ipconfig.o
>>about 13K.
>>
>
> There's a cap on the maximum size of things various bootloaders can
> load via tftp; 2MB is relatively certain to blow it. ISTR the limit
> being something near 1MB for 2 of my boxen.
Since this is totally machine/architecture specific (we're tftp'ing 10MB
kernel/ramdisk images to embedded PPC machines here) it might be a good
idea to ask around and find what the most restrictive requirements are.
Is 1MB the worst-case or does it get even tighter?
Chris
--
Chris Friesen | MailStop: 043/33/F10
Nortel Networks | work: (613) 765-0557
3500 Carling Avenue | fax: (613) 765-2986
Nepean, ON K2H 8E9 Canada | email: cfriesen@nortelnetworks.com
next prev parent reply other threads:[~2003-03-07 22:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 21:10 Make ipconfig.c work as a loadable module Robin Holt
2003-03-06 22:34 ` Alan Cox
2003-03-06 22:11 ` Jeff Garzik
2003-03-06 22:25 ` Russell King
2003-03-06 22:32 ` Jeff Garzik
2003-03-07 0:13 ` Alan Cox
2003-03-06 23:19 ` Russell King
2003-03-07 0:29 ` Alan Cox
2003-03-07 0:08 ` Russell King
2003-03-07 1:29 ` Chris Dukes
2003-03-07 9:42 ` Russell King
2003-03-07 11:46 ` Bogdan Costescu
2003-03-08 2:03 ` Eric W. Biederman
2003-03-08 10:45 ` Bogdan Costescu
2003-03-08 16:07 ` Eric W. Biederman
2003-03-08 16:19 ` Russell King
2003-03-08 16:48 ` Eric W. Biederman
2003-03-08 17:05 ` Russell King
2003-03-08 18:01 ` Eric W. Biederman
2003-03-07 13:38 ` Chris Dukes
2003-03-07 14:29 ` Russell King
2003-03-07 16:23 ` Richard B. Johnson
2003-03-07 21:47 ` William Lee Irwin III
2003-03-07 22:00 ` Chris Friesen [this message]
2003-03-07 7:15 ` Michael Mueller
2003-03-07 12:54 ` Alan Cox
2003-03-07 21:33 ` Michael Mueller
2003-03-09 4:46 ` Arnaldo Carvalho de Melo
2003-03-07 9:10 ` Denis Vlasenko
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=3E69166F.9080604@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=holt@sgi.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=pakrat@www.uk.linux.org \
--cc=wli@holomorphy.com \
/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).