Theodore Tso <[EMAIL PROTECTED]> wrote: > > The question is whether the size of the Unix domain sockets support is > worth the complexity of yet another config option that we expose to > the user. For the embedded world, OK, maybe they want to save 14k of > non-swappable memory. But for the non-embedded world, given the 117k > mandatory memory usage of sysfs, or the 124k memory usage of the core > networking stack, never mind the 3 megabytes of memory used by objects > in the kernel subdirectory, it's not clear that it's worth worrying > over 14k of memory, especially when many Unix programs assume > that Unix Domain Sockets are present.
That would make sense if we were proposing to get rid of the CONFIG_UNIX question altogether for !CONFIG_EMBEDDED. However, the proposal here is merely to eliminate the modular option but the CONFIG_UNIX prompt itself will remain even without CONFIG_EMBEDDED. This I think is quite pointless. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
