From: Theodore Tso <tytso@mit.edu>
To: Bodo Eggert <7eggert@gmx.de>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
David Miller <davem@davemloft.net>,
jengelh@computergmbh.de, devzero@web.de,
linux-kernel@vger.kernel.org, bunk@kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH] Force UNIX domain sockets to be built in
Date: Tue, 1 Jan 2008 00:01:54 -0500 [thread overview]
Message-ID: <20080101050154.GG11776@mit.edu> (raw)
In-Reply-To: <alpine.LSU.0.999.0801010418260.2337@be1.lrz>
On Tue, Jan 01, 2008 at 04:45:21AM +0100, Bodo Eggert wrote:
> > udev-free != embedded.
>
> But UNIX=m == waste RAM and have an effectively b0rken system until the
> module is loaded.
Well, the system isn't necessarily totally broken. If you don't use
udev, then system will be crippled, but not totally broken. Then
again, besides udev, packages such as dbus, gdm, and acpid all use
Unix Domain Sockets --- not to mention cups, avahi-daemon, bluez,
emacsclient, and any X program when the DISPLAY is :0.0.
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.
- Ted
next prev parent reply other threads:[~2008-01-01 5:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 12:09 [PATCH] Force UNIX domain sockets to be built in Bodo Eggert
2007-12-31 12:20 ` David Miller
2007-12-31 14:03 ` Bodo Eggert
2007-12-31 19:38 ` Al Viro
2008-01-01 3:45 ` Bodo Eggert
2008-01-01 3:48 ` David Miller
2008-01-01 4:48 ` Bodo Eggert
2008-01-01 5:01 ` Theodore Tso [this message]
2008-01-02 10:25 ` Herbert Xu
2008-01-02 12:26 ` Bodo Eggert
2007-12-31 12:24 ` Adrian Bunk
2007-12-31 13:26 ` Bodo Eggert
2007-12-31 14:42 ` Adrian Bunk
2007-12-31 15:19 ` Bodo Eggert
2007-12-31 15:34 ` Jan Engelhardt
2007-12-31 17:43 ` Patrick Mau
2007-12-31 22:20 ` Jan Engelhardt
2007-12-31 17:51 ` Adrian Bunk
2007-12-31 18:05 ` Adrian Bunk
2007-12-31 15:55 ` Torsten Kaiser
2007-12-31 15:59 ` Michael Buesch
2007-12-31 16:01 ` Alan Cox
2007-12-31 16:17 ` Torsten Kaiser
2007-12-31 16:38 ` Alan Cox
2007-12-31 17:18 ` Michael Buesch
2007-12-31 18:37 ` Torsten Kaiser
2007-12-31 19:05 ` Michael Buesch
2007-12-31 16:11 ` Torsten Kaiser
-- strict thread matches above, loose matches on Subject: below --
2007-12-31 13:23 devzero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080101050154.GG11776@mit.edu \
--to=tytso@mit.edu \
--cc=7eggert@gmx.de \
--cc=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=devzero@web.de \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).