summaryrefslogtreecommitdiff
path: root/microkernel/mach/gnumach/projects.mdwn
diff options
context:
space:
mode:
authorThomas Schwinge <tschwinge@gnu.org>2008-04-29 14:14:19 +0200
committerThomas Schwinge <tschwinge@gnu.org>2008-04-29 14:14:19 +0200
commite5a3be83f30e7926a66ebfe40884e5fb5fc1bd69 (patch)
tree19feb53912d9ff0850def67e07a970f590c3b21c /microkernel/mach/gnumach/projects.mdwn
parent01af632a76ee8685d5db281c7805255a1b7c57d6 (diff)
Indenting.
Diffstat (limited to 'microkernel/mach/gnumach/projects.mdwn')
-rw-r--r--microkernel/mach/gnumach/projects.mdwn89
1 files changed, 45 insertions, 44 deletions
diff --git a/microkernel/mach/gnumach/projects.mdwn b/microkernel/mach/gnumach/projects.mdwn
index 1c45d169..e0b6572c 100644
--- a/microkernel/mach/gnumach/projects.mdwn
+++ b/microkernel/mach/gnumach/projects.mdwn
@@ -31,78 +31,79 @@ so that no duplicate efforts end up.
# Task List
-* [[Clean_up_the_code]]
+ * [[Clean_up_the_code]]
-* Update the core architecture and drivers
+ * Update the core architecture and drivers
- * Check what NetBSD, FreeBSD and Linux do with their host specific code
- (i486, PPC, Sparc, ...). And if it might be wise to take that and use it
- in GNU Mach. There is no need to worry about purely internal API's, but
- the external ones shouldn't require any major changes.
+ * Check what NetBSD, FreeBSD and Linux do with their host specific code
+ (i486, PPC, Sparc, ...). And if it might be wise to take that and use
+ it in GNU Mach. There is no need to worry about purely internal API's,
+ but the external ones shouldn't require any major changes.
- * Write a list of all functions provided by the host dependant code in GNU
- Mach that gets used in the non-host specific code (kernel, IPC and VM).
+ * Write a list of all functions provided by the host dependant code in
+ GNU Mach that gets used in the non-host specific code (kernel, IPC and
+ VM).
- * Once we have decided what the new internal API should look like, make a
- list of the new API and the old one, and try to make things as compatible
- as possible, but not at the expense of anything.
+ * Once we have decided what the new internal API should look like, make a
+ list of the new API and the old one, and try to make things as
+ compatible as possible, but not at the expense of anything.
-* Implement Migrating Threads
+ * Implement Migrating Threads
- * Migrating Threads (MT) could improve IPC performance and making easier the
- work of the scheduler. For more information, check
- <http://www.usenix.org/publications/library/proceedings/sf94/ford.html>
+ * Migrating Threads (MT) could improve IPC performance and making easier
+ the work of the scheduler. For more information, check
+ <http://www.usenix.org/publications/library/proceedings/sf94/ford.html>
-* Improve the external pagers interface
+ * Improve the external pagers interface
- * Making this interface synchronous should improve I/O performance
- significantly, without (almost) any drawbacks (we also get some advantage
- from MT's).
+ * Making this interface synchronous should improve I/O performance
+ significantly, without (almost) any drawbacks (we also get some
+ advantage from MT's).
- * Implement more paging eviction policies, so they fit better with usual
- behaviour of the pagers.
+ * Implement more paging eviction policies, so they fit better with usual
+ behaviour of the pagers.
- * Implement resource accounting for external pagers.
+ * Implement resource accounting for external pagers.
-* VM
+ * VM
- * Put it on user level (?)
+ * Put it on user level (?)
- * Clean up the mess.
+ * Clean up the mess.
- * Provide a fast way to read/write from/to a memory object.
+ * Provide a fast way to read/write from/to a memory object.
- * Simplify/normalise the code.
+ * Simplify/normalise the code.
-* Simplify the IPC Semantics
+ * Simplify the IPC Semantics
- * There are a lot of things in GNU Mach's IPC that we don't need. Track down
- those things, and get rid of them without requiring many changes in the
- Hurd (the changes will affect MiG, but that is OK).
+ * There are a lot of things in GNU Mach's IPC that we don't need. Track
+ down those things, and get rid of them without requiring many changes
+ in the Hurd (the changes will affect MiG, but that is OK).
-* Temporary mappings for Client-Server memory transfers
+ * Temporary mappings for Client-Server memory transfers
- * Extend Mach's IPC to provide some kind of object which can represent a
- range of memory that can temporarily be mapped into the servers address
- space for sending/receiving data. This would allow us to avoid excessive
- memory copies.
+ * Extend Mach's IPC to provide some kind of object which can represent a
+ range of memory that can temporarily be mapped into the servers address
+ space for sending/receiving data. This would allow us to avoid
+ excessive memory copies.
- * Find a new way to work with unaligned memory.
+ * Find a new way to work with unaligned memory.
-* GDB remote debugging support
+ * GDB remote debugging support
- * Implement support for GDB debugging via serial line and/or network. Maybe
- this can be done together with the host-specific work above.
+ * Implement support for GDB debugging via serial line and/or network.
+ Maybe this can be done together with the host-specific work above.
See [[GDB_stubs]].
# Wish List
-* Interface for userspace non-critical drivers.
+ * Interface for userspace non-critical drivers.
-* Sound Support
+ * Sound Support
-* WLAN support (ipw2200) with WEP/WPA
+ * WLAN support (ipw2200) with WEP/WPA
-* ACPI support
+ * ACPI support