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
| ||
|
Date: Tue, 6 May 2014 09:18:25 +0000 From: David Laight <David.Laight@...LAB.COM> To: 'Andi Kleen' <andi@...stfloor.org>, "netdev@...r.kernel.org" <netdev@...r.kernel.org> CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "tom.zanussi@...ux.intel.com" <tom.zanussi@...ux.intel.com> Subject: RE: A reduced Linux network stack for small systems From: Andi Kleen > There has been a lot of interest recently to run Linux on very small systems, > like Quark systems. These may have only 2-4MB memory. They are also limited > by flash space. I'm intrigued about the 2-4MB memory. That is more that would typically be available on-chip in a DSP or FPGA. It sounds like an expensive SRAM chip. OTOH a single SDRAM gives 16MB and DDR a lot more - and are a lot cheaper and lower power. Most modern silicon can easily have SDRAM/DDR interfaces. You may want some size reduction to run in 16MB, but it is not as problematic as running in 2MB. With that little memory I wouldn't want to run anything that relied on dynamic memory allocation (after startup) - except for fixed size data buffers. David -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists