From b6e8513dc624ee96954e1fa4493cdb497f54b865 Mon Sep 17 00:00:00 2001 From: BobHam Date: Sun, 29 Sep 2013 15:53:42 +0200 Subject: Creating page on x15 --- x15.mdwn | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) create mode 100644 x15.mdwn diff --git a/x15.mdwn b/x15.mdwn new file mode 100644 index 00000000..123c2cd4 --- /dev/null +++ b/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. -- cgit v1.2.3 From 606b5801f725b4fc6cab1ec0342a9298a8e92a9d Mon Sep 17 00:00:00 2001 From: BobHam Date: Sun, 29 Sep 2013 15:54:56 +0200 Subject: rename x15.mdwn to microkernel/x15.mdwn --- microkernel/x15.mdwn | 24 ++++++++++++++++++++++++ x15.mdwn | 24 ------------------------ 2 files changed, 24 insertions(+), 24 deletions(-) create mode 100644 microkernel/x15.mdwn delete mode 100644 x15.mdwn 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. diff --git a/x15.mdwn b/x15.mdwn deleted file mode 100644 index 123c2cd4..00000000 --- a/x15.mdwn +++ /dev/null @@ -1,24 +0,0 @@ -[[!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. -- cgit v1.2.3 From 39aa390a36507f5779b87d21dd93f9b734b62f0b Mon Sep 17 00:00:00 2001 From: BobHam Date: Sun, 29 Sep 2013 15:56:31 +0200 Subject: Adding link to page about braunr's x15 microkernel --- microkernel.mdwn | 2 ++ 1 file changed, 2 insertions(+) diff --git a/microkernel.mdwn b/microkernel.mdwn index c7fc0995..7c0e34c2 100644 --- a/microkernel.mdwn +++ b/microkernel.mdwn @@ -57,3 +57,5 @@ A 2002 article about [[microkernel_FUD|FUD]] (Fear, Uncertainty, Doubt). * [[Viengoos]] * [[Genode]] + + * [[x15]] -- cgit v1.2.3 From 9061995e3454f933b80a263cc688b1303da599a7 Mon Sep 17 00:00:00 2001 From: BobHam Date: Sun, 29 Sep 2013 16:06:26 +0200 Subject: Minor edits for style --- microkernel/x15.mdwn | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/microkernel/x15.mdwn b/microkernel/x15.mdwn index 123c2cd4..b56c97fc 100644 --- a/microkernel/x15.mdwn +++ b/microkernel/x15.mdwn @@ -14,11 +14,11 @@ The following specific features are intended to distinguish x15 from other micro * 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. +* 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 GNU Mach 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 +* A restriction on IPC that only allows reliable transfers across network to machines with same arch and endianness * etc. -- cgit v1.2.3