From 6f9c0342f33f52a2bda98d3709fbefd678bd46d9 Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 13 May 2012 06:06:11 +0200 Subject: IRC. --- hurd/translator/devfs.mdwn | 36 ++++++++++++- hurd/translator/ext2fs.mdwn | 13 +++-- .../ext2fs/hurd-specific_extensions.mdwn | 23 ++++++++ hurd/translator/ext2fs/page_cache.mdwn | 31 +++++++++++ hurd/translator/procfs/jkoenig/discussion.mdwn | 61 +++++++++++++++++++++- 5 files changed, 158 insertions(+), 6 deletions(-) create mode 100644 hurd/translator/ext2fs/hurd-specific_extensions.mdwn create mode 100644 hurd/translator/ext2fs/page_cache.mdwn (limited to 'hurd/translator') diff --git a/hurd/translator/devfs.mdwn b/hurd/translator/devfs.mdwn index 8784e998..a9cc307f 100644 --- a/hurd/translator/devfs.mdwn +++ b/hurd/translator/devfs.mdwn @@ -12,7 +12,7 @@ License|/fdl]]."]]"""]] in there in a dynamic fashion -- as compared to static passive translator settings as they're used now. -`devfs` has not yet been written. +`devfs` has not yet been written. [[!tag open_issue_hurd]] --- @@ -23,6 +23,8 @@ path is resident at all times. # IRC, freenode, #hurd, 2012-01-29 +[[!tag open_issue_documentation]] + what would be an hurdish way to achieve something like the various system (udev, devfs, devd, etc) for populating devices files automatically according to the found system devices? @@ -37,3 +39,35 @@ path is resident at all times. /dev directory with unique device names... probably need some unionfs-like translator that collects the individual driver nodes in an intelligent manner + + +# IRC, freenode, #hurd, 2012-04-22 + + braunr: I don't think it's a problem that translators are invoked + when listing /dev + the problem is that they linger around although they are very + unlikely to be needed again any time soon + for now it's not too much a problem because there aren't too many + but that can become problematic + a devfs on /dev could also fill it with new devices + but only with the ones that actually exist + yeah + antrik: i mean, the hurd may lack a feature allowing the same + translator to be used for several nodes not hierarically related + antrik: or rather, it's a special case that we should implement + differently + (with e.g. a devfs that can route requests for different nodes to + a same translator + ) + I agree BTW that some intermediary for /dev would be helpful -- + but I don't think it should actually take over any RPC handling; rather, + only redirect the requests as appropriate (with the actual device nodes + in a hierarchical bus-centric layout) + right + braunr: actually, the Hurd *does* have a feature allowing the same + translator to be attached to several unrelated nodes + i keep getting surprised :) + though it's only used in very few places right now + pfinet and ptys at least ? + yeah, and console client IIRC + diff --git a/hurd/translator/ext2fs.mdwn b/hurd/translator/ext2fs.mdwn index fff2e74b..ad79c7b9 100644 --- a/hurd/translator/ext2fs.mdwn +++ b/hurd/translator/ext2fs.mdwn @@ -1,18 +1,23 @@ -[[!meta copyright="Copyright © 2007, 2008, 2010, 2011 Free Software Foundation, -Inc."]] +[[!meta copyright="Copyright © 2007, 2008, 2010, 2011, 2012 Free Software +Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license -is included in the section entitled -[[GNU Free Documentation License|/fdl]]."]]"""]] +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + # Implementation * [[filetype]] option + * [[Hurd-specific_extensions]] + + * [[Page_cache]] + ## Large Stores diff --git a/hurd/translator/ext2fs/hurd-specific_extensions.mdwn b/hurd/translator/ext2fs/hurd-specific_extensions.mdwn new file mode 100644 index 00000000..774f1cf3 --- /dev/null +++ b/hurd/translator/ext2fs/hurd-specific_extensions.mdwn @@ -0,0 +1,23 @@ +[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!tag open_issue_documentation]] + + +# IRC, freenode, #hurd, 2012-04-20 + + what are the extensions to ext2? + that hurd uses + tha ability to store passive translator command lines in the + inodes + the* + well, also a fourth set of permission bits, and an "author" field + right + both very obscure features that better never existed... diff --git a/hurd/translator/ext2fs/page_cache.mdwn b/hurd/translator/ext2fs/page_cache.mdwn new file mode 100644 index 00000000..e8a964ed --- /dev/null +++ b/hurd/translator/ext2fs/page_cache.mdwn @@ -0,0 +1,31 @@ +[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]] + +[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable +id="license" text="Permission is granted to copy, distribute and/or modify this +document under the terms of the GNU Free Documentation License, Version 1.2 or +any later version published by the Free Software Foundation; with no Invariant +Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license +is included in the section entitled [[GNU Free Documentation +License|/fdl]]."]]"""]] + +[[!tag open_issue_documentation]] + +This is not at all specific to ext2fs, so should be integrated elsewhere. + + +# IRC, freenode, #hurd, 2012-04-22 + + is there any particular reason ext2fs takes so much memory? + it beats everything on my system hands down at 100 MB + ext2fs contains the page cache + so it's no wonder it takes memory + it's all the mapped files + any way I can cut down on that? + my system only has 512 meg :/ + gnumach is supposed to automatically cut it down as needed + what is the actual symptom that you see? + youpi: 360 MB of memory usage when I'm doing nothing + oh, is it just intelligent enough to cut down when I'm using more + memory? + Tekk_: yes + awesome. I was worried :) diff --git a/hurd/translator/procfs/jkoenig/discussion.mdwn b/hurd/translator/procfs/jkoenig/discussion.mdwn index 339fab50..e7fdf46e 100644 --- a/hurd/translator/procfs/jkoenig/discussion.mdwn +++ b/hurd/translator/procfs/jkoenig/discussion.mdwn @@ -1,4 +1,5 @@ -[[!meta copyright="Copyright © 2010, 2011 Free Software Foundation, Inc."]] +[[!meta copyright="Copyright © 2010, 2011, 2012 Free Software Foundation, +Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this @@ -218,3 +219,61 @@ Needed by glibc's `pldd` tool (commit # `/proc/self/exe` [[!message-id "alpine.LFD.2.02.1110111111260.2016@akari"]] + + +# `/proc/[PID]/fd/` + +## IRC, freenode, #hurd, 2012-04-24 + + braunr: /proc/*/fd can be implemented in several ways. none of + them would require undue centralisation + braunr: the easiest would be adding one more type of magic lookup + to the existing magic lookup mechanism + wait, I mean /proc/self... for /proc/*/fd it's even more + straighforward -- we might even have a magic lookup for that already + i guess the ideal thing would be implement that fd logic in + libps + pinotree: nope. it doesn't need to ask proc (or any other server) + at all. it's local information. that's what we have the magic lookups for + one option we were considering at some point would be using the + object migration mechanism, so the actual handling would still happen + client-side, but the server could supply the code doing it. this would + allow servers to add arbitrary magic lookup methods without any global + modifications... but has other downsides :-) + youpi: How much info for /proc/*/fd is possible to get from + libps? Re: d-h@ + see my mail + I don't think there is an interface for that + processes handle fds themselves + so libps would have to peek in there + and I don't remember having seen any code like that + 10:17:17< antrik> wait, I mean /proc/self... for /proc/*/fd it's + even more straighforward -- we might even have a magic lookup for that + already + pinotree: For me that does not ring a bell on RPCs. Don't know + what magic means,, + for /proc/self/fd we have a magic lookup + for /proc/pid/fd, I don't think we have + magic lookup* + magic lookup == RPC? + magic lookup is a kind of answer to the lookup RPC + that basically says "it's somewhere else, see there" + the magic FD lookup tells the process "it's your FD number x" + which works for /proc/self/fd, but not /proc/pid/fd + youpi, gnu_srs: regarding FDs, there the msg_get_fd RPC that + could be used + `msgport' should have --get-fd, actually + civodul: I assumed that the reason why msgport doesn't have it is + that it didn't exist + so we can get a port on the fd + but then how to know what it is? + youpi: ah, you mean for the /proc/X/fd symlinks? + good question + it's not designed to be mapped back to names, indeed :-) + youpi: yeah, I realized myself that only /proc/self/fd is trivial + BTW, in Linux it's nor real symlinks. it's magic, with some very + strange (but useful in certain situations) semantics + not real symlinks + it's very weird for example for fd connected to files that have + been unlinked. it looks like a broken symlink, but when dereferencing + (e.g. with cp), you get the actual file contents... -- cgit v1.2.3