From: kunaguero Date: Thu, 9 Jan 2014 03:15:18 +0000 (+0000) Subject: No commit message specified. X-Git-Url: https://gitweb.dragonflybsd.org/ikiwiki.git/commitdiff_plain/74ffe821c1c373417d6cb20d9edb4c4030203d47 No commit message specified. --- diff --git a/features/index.mdwn b/features/index.mdwn index bb5d290a..bef3df6f 100644 --- a/features/index.mdwn +++ b/features/index.mdwn @@ -9,6 +9,7 @@ Please keep in mind that major modifications have been made to nearly the entire * The scheduler abstraction has been split up into two layers. The LWKT (Light Weight Kernel Thread) scheduler is used by the kernel to schedule all executable entities. The User Thread Scheduler is a separate scheduler which selects one user thread at a time for each cpu and schedules it using the LWKT scheduler. Both scheduler abstractions are per-cpu but the user thread scheduler selects from a common list of runnable processes. * The User Thread Scheduler further abstracts out user threads. A user process contains one or more LWP (Light Weight Process) entities. Each entity represents a user thread under that process. The old rfork() mechanism still exists but is no longer used. The threading library uses LWP-specific calls. +[Sewa mobil jakarta](http://www.awanirentcar.com/pricelist), [Aksesoris mobil](http://kiosauto.com), [Toko bunga online](http://www.tokobungasabana.com), [Gps tracker mobil](http://vamostech.com/gps-tracking), [Gps tracking kapal](http://vamostech.com/gps-tracking), [Cotton bud](http://www.mitracatur.com/product/cotton-bud) * The kernel memory allocator has two abstracted pieces. The basic kernel malloc is called kmalloc() and is based on an enhanced per-cpu slab allocator. This allocator is essentially lockless. There is also an object-oriented memory allocator in the kernel called objcache which is designed for high volume object allocations and deallocations and is also essentially lockless.