On 10/4/11 03:10 , Henk Uijterwaal wrote: > On 03/10/2011 18:50, Lorenzo Colitti wrote: >> On Mon, Oct 3, 2011 at 08:58, Randy Turner <[email protected] >> <mailto:[email protected]>> wrote: >> >> I would hope that we would NOT be seriously considering OSPF or IS-IS in >> the >> home...this seems like using a sledgehammer to kill an ant. >> >> >> If the devices we're talking about have enough resources to run them, and >> they >> have desirable properties that are useful in home networks, then what's the >> problem with either of these? Home gateways these days are capable of 1Gbps >> hardware forwarding and have pretty fast CPUs. > > The problem isn't the CPU but the memory. Vendors want to stick in as little > (expensive) flash and RAM as possible, and don't want to spend a few $$ for > a few spare meg's of memory that won't be used by most of the customers. > > I've created new images for these devices and whenever adding something, > one also had to ask the question what to drop in order for the new code > to fit. Adding memory generally wasn't an option.
one can handily demonstrate ospfv2 and v3 running on an off the shelf wireless ap platform with 16MB of ram along with the utility necessary to make it a functional ap/home-gateway. while memory is or can be tight there are other functional requirements driving memory utilization as well and how much ram they are built will depend on the need to pack features in to remain competitive. IF the could optimize the BOM down to a rock in a box they would but stateful inspection policy, gigabit ethernet/802.11n mimo buffers usb ports/support storage/media gateway functionality/ipv6 support etc all conspire to make the ap you have now have more resources than the one you had in the past. > Henk > > _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
