Date: Fri, 7 Dec 2012 15:38:36 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Warner Losh <imp@bsdimp.com> Cc: Alfred Perlstein <bright@mu.org>, Andre Oppermann <andre@freebsd.org>, Alfred Perlstein <alfred@freebsd.org>, freebsd-arch@freebsd.org Subject: Re: svn commit: r243594 - head/sys/netinet Message-ID: <CAJ-VmokjzMxpY0hpxGLq4_yy3tU29JcCTZi8PChn8t7hmbcn8Q@mail.gmail.com> In-Reply-To: <52564974-563C-499F-9860-ADACA0DD22CE@bsdimp.com> References: <201211270304.qAR34PfD056691@svn.freebsd.org> <50B53ABC.1010304@freebsd.org> <50B57F46.1060207@mu.org> <50C205DC.1040701@freebsd.org> <AC499CCF-3812-4CA9-929C-05AA4C39F223@mu.org> <50C23B5E.3020509@freebsd.org> <50C26BF9.1050106@mu.org> <CAJ-Vmo=okfoDzUSBJ%2B1=iq44EaNw_uOWCOTB-7TVU6%2BdFZeFyA@mail.gmail.com> <50C278B0.3040107@mu.org> <52564974-563C-499F-9860-ADACA0DD22CE@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
..right. I could spin the argument back to you Alfred and say "make the default compile time settings for i386/amd64/sparc64 GENERIC to have bigger TCP hash sizes, default mbuf tuning, larger kernel dmesg buffer sizes, increased mutex hash table sizes, etc, and leave the defaults as they are. What I'm trying to say/encourage is some more even-handed ways of doing this, rather than "hey, it works in the server world, that's all that matters, right?" And FYI - installation on embedded devices these days is "open device web page, upload firmware image, hit "flash", reboot." That's what openwrt and dd-wrt do for the majority of their platforms. No serial console required. As I said, I don't think everyone invested in this is seeing the bigger picture and trying to work out whether we can solve this in a better fashion. The peeps in the Linux world _have_ come up with _a_ solution that seems to work. So it's not that its intractable. Adrian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmokjzMxpY0hpxGLq4_yy3tU29JcCTZi8PChn8t7hmbcn8Q>