summaryrefslogtreecommitdiff
path: root/microkernel
diff options
context:
space:
mode:
authorBobHam <BobHam@web>2013-09-29 15:54:56 +0200
committerGNU Hurd web pages engine <web-hurd@gnu.org>2013-09-29 15:54:56 +0200
commit606b5801f725b4fc6cab1ec0342a9298a8e92a9d (patch)
tree3f2f996a810866813cf383d4444c0d66b42812c6 /microkernel
parentb6e8513dc624ee96954e1fa4493cdb497f54b865 (diff)
rename x15.mdwn to microkernel/x15.mdwn
Diffstat (limited to 'microkernel')
-rw-r--r--microkernel/x15.mdwn24
1 files changed, 24 insertions, 0 deletions
diff --git a/microkernel/x15.mdwn b/microkernel/x15.mdwn
new file mode 100644
index 00000000..123c2cd4
--- /dev/null
+++ b/microkernel/x15.mdwn
@@ -0,0 +1,24 @@
+[[!meta copyright="Copyright © 2013 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]]."]]"""]]
+
+The x15 microkernel is under development by Richard Braun. Overall, x15 is intended to provide better performance because of simpler IPC and data structures and better scalability because of improved data structure algorithms and concurrency.
+
+The following specific features are intended to distinguish x15 from other microkernels. However, it should be noted that the microkernel is under heavy development and so the list may (and almost certainly will) change.
+
+* SMP support
+* Lockless synchronisation à la RCU
+* Support for large amounts of physical memory. GNU Mach does the same as Linux, physical memory is mapped in kernel space so you can't have more physical memory than you have kernel space which is why gnumach can't handle more than 1.8G right now, it's a 2/2 split. In x15, the kernel maps what it needs and can map it from anywhere in physical memory the drawback is that it needs to update kernel page tables more often.
+* Virtual memory operations are planned to be completely concurrent on x15, similar to what is described in radixvm
+* Intended to efficiently run a Hurd-like system providing a POSIX interface
+* Providing both synchronisation IPC and signals, as opposed to just synchronisation IPC
+* Port names which will transparently identify as file descriptors
+* Light reference counting
+* A restriction on ipc that only allows reliable transfers across network to machines with same arch and endianness
+* etc.