diff options
author | Thomas Schwinge <tschwinge@gnu.org> | 2008-04-02 17:14:37 +0200 |
---|---|---|
committer | Thomas Schwinge <tschwinge@gnu.org> | 2008-04-02 17:14:37 +0200 |
commit | 6a033288e4604e8ed2532573a80fd1114a7e1b68 (patch) | |
tree | 4d8c9af48d38a00b01cc82e05f2db786680095cf | |
parent | 5b41f2e4140e4d08699b432271c2741b988ee0c5 (diff) |
Start new page about the *resource management problems*.
-rw-r--r-- | hurd/ng/history.mdwn | 9 | ||||
-rw-r--r-- | hurd/ng/resource_management_problems.mdwn | 19 |
2 files changed, 25 insertions, 3 deletions
diff --git a/hurd/ng/history.mdwn b/hurd/ng/history.mdwn index b6008eec..652bccf3 100644 --- a/hurd/ng/history.mdwn +++ b/hurd/ng/history.mdwn @@ -10,11 +10,11 @@ is included in the section entitled The idea of using [[microkernel/L4]] as a [[microkernel]] for a [[Hurd_system|hurd]] was initially voiced in the [[Hurd_community|community]] -by Okuji Yoshinori. He created the *[[mailing_lists/l4-hurd]]* mailing list in +by Okuji Yoshinori. He created the [[mailing_lists/l4-hurd]] mailing list in November 2000. It does not appear that he got any further than simply suggesting it as an alternative to [[microkernel/Mach]] and doing some reading. -[[NealWalfield]] started the original Hurd/L4 port while at Karlsruhe in 2002. +Neal Walfield started the original Hurd/L4 port while at Karlsruhe in 2002. He explains: > My intention was to adapt the Hurd to exploit L4's concepts and intended @@ -29,7 +29,7 @@ He explains: > half of 2004, after I complete by Bachelors degree. > Before Marcus and I considered [[microkernel/Coyotos]], we had already -> rejected some parts of the Hurd's design. The resource management problems +> rejected some parts of the Hurd's design. The [[resource_management_problems]] > were what prompted me to look at L4. Also, some of the problems with > [[translator]]s were already well-known to us. (For a more detailed > description of the problems we have identified, see our [[critique]] in the @@ -41,6 +41,9 @@ He explains: > aligned our position with that of Jonathan's. This was particularly true of > a number of security issues. +A lange number of discussion threads can be found in the archives of the +[[mailing_lists/l4-hurd]] mailing list. + > Hurd-NG, as we originally called it, was an attempt to articulate the system > that we had come to envision in terms of interfaces and description of the > system's structure. The new name was selected, if I recall correctly, as it diff --git a/hurd/ng/resource_management_problems.mdwn b/hurd/ng/resource_management_problems.mdwn new file mode 100644 index 00000000..856afb1a --- /dev/null +++ b/hurd/ng/resource_management_problems.mdwn @@ -0,0 +1,19 @@ +[[meta copyright="Copyright © 2008 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]]."]]"""]] + +[[microkernel/Mach]] interfaces do not allow for proper resource accounting, +when a server allocates resources on behalf of a client. + +Mach can't do a good job at resource management, as it doesn't have enough +information how resources are used: which data is important and which is +discardable, for example. + +These issues are what Neal Walfield is working on with his new kernel +[[microkernel/viengoos]]. |