netdev - Re: [PATCH] dnet: Dave DNET ethernet controller driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090312215919.GA19200@shareable.org>
Date:	Thu, 12 Mar 2009 21:59:19 +0000
From:	Jamie Lokier <jamie@...reable.org>
To:	Neil Horman <nhorman@...driver.com>
Cc:	Christer Weinigel <christer@...nigel.se>,
	David Miller <davem@...emloft.net>, shemminger@...tta.com,
	s.hauer@...gutronix.de, yanok@...raft.com,
	linux-arm-kernel@...ts.arm.linux.org.uk, netdev@...r.kernel.org,
	wd@...x.de, dzu@...x.de
Subject: Re: [PATCH] dnet: Dave DNET ethernet controller driver

Neil Horman wrote:
> I've not looked at the figures lately, but how much space does the
> dhcp client and nfs root code take up in the kernel these days?

About 4k apparently.  See the difference from "400k compressed?".
Also, uncompressing that may add 0.5 second boot time on a slow CPU :-)

> I sympathize with you.  This is exactly what soured me on embedded
> work a few years back.  Embedded shops are forever compromising
> doing things correctly in the name of time and schedules, never
> paying any heed to the possibility that taking extra time to do
> things in an agreed upon, organized and standard fashion might pay
> off for them in the long run.

I must admit that a solution which makes the effective kernel size
800k larger (your figure) doesn't look like a good standard to me.

If that was the "standard", I'd be tempted to add a MAC address driver
hack to the kernel to save the space :-)

-- Jamie
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html