Hi all, The review of Boost.Fiber by Oliver Kowalke is scheduled from Monday, January 6th to January 12th. ----------------------------------------------------- About the library: Boost.Fiber provides a framework for micro-/userland-threads (fibers) scheduled cooperatively. The API contains classes and functions to manage and synchronize fibers similar to Boost.Thread. Each fiber has its own stack. A fiber can save the current execution state, including all registers and CPU flags, the instruction pointer, and the stack pointer and later restore this state. The idea is to have multiple execution paths running on a single thread using a sort of cooperative scheduling (versus threads, which are preemptively scheduled). The running fiber decides explicitly when it should yield to allow another fiber to run (context switching). Boost.Fiberinternally uses coroutines from Boost.Coroutine <http://ok73.funpic.de/boost/libs/coroutine/index.html>; the classes in this library manage, schedule and, when needed, synchronize those coroutines. A context switch between threads usually costs thousands of CPU cycles on x86, compared to a fiber switch with a few hundred cycles. A fiber can only run on a single thread at any point in time. docs: http://ok73.funpic.de/boost/libs/fiber/doc/html/index.html<http://ok73.ok.funpic.de/boost/libs/coroutine/doc/html/> git: https://github.com/olk/boost-fiber src: http://ok73.ok.funpic.de/boost.fiber.zip<http://ok73.ok.funpic.de/boost.coroutine.zip> --------------------------------------------------- Naturally, you need not wait until the review formally opens to start reviewing the Fiber library. Please always state in your review whether you think the library should be accepted as a Boost library! Additionally please consider giving feedback on the following general topics: - What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Nat Goodspeed Boost.Fiber Review Manager ------------------------------
On Wed, Dec 18, 2013 at 8:03 PM, Nat Goodspeed <nat@lindenlab.com> wrote:
Hi all,
The review of Boost.Fiber by Oliver Kowalke is scheduled from Monday, January 6th to January 12th.
Hi Nat and Oliver, I'm quite interested in reviewing this library, but the hosted documentation has obnoxious undismissable (the close button just opens another windows) randomly appearing ads that cover the text, which make reading the docs a chore. Would it be possible to get the docs hosted somewhere else? Thanks, -- gpd
2013/12/20 Giovanni Piero Deretta <gpderetta@gmail.com>
On Wed, Dec 18, 2013 at 8:03 PM, Nat Goodspeed <nat@lindenlab.com> wrote:
Hi all,
The review of Boost.Fiber by Oliver Kowalke is scheduled from Monday, January 6th to January 12th.
Hi Nat and Oliver,
I'm quite interested in reviewing this library, but the hosted documentation has obnoxious undismissable (the close button just opens another windows) randomly appearing ads that cover the text, which make reading the docs a chore.
Would it be possible to get the docs hosted somewhere else?
Hello Giovanni, it's a free webhoster and I didn't noticed those popup-windows because I'm using Adblock in my firefox. If you know a free webhoster without such 'advertisements' I would copy the documentation too. Alternatively - the zip-Archive already contains the html-pages. best, Oliver
On 12/20/2013 01:34 PM, Oliver Kowalke wrote:
If you know a free webhoster without such 'advertisements' I would copy the documentation too.
http://pages.github.com/ http://sourceforge.net/p/forge/documentation/Project%20Web%20Services/
If you know a free webhoster without such 'advertisements' I would copy the documentation too. Alternatively - the zip-Archive already contains the html-pages.
I have put the html part of the .zip at http://www.voti.nl/fibre . Some pictures seem to be missing, but the text is there. @Oliver: if you can send me a .zip with the pictures I can upload it. Wouter.* *
I have put the html part of the .zip at http://www.voti.nl/fibre .
That should have been http://www.voti.nl/fiber , sorry. Wouter
2013/12/20 Wouter van Ooijen <wouter@voti.nl>
If you know a free webhoster without such 'advertisements' I would copy the documentation too. Alternatively - the zip-Archive already contains the html-pages.
I have put the html part of the .zip at http://www.voti.nl/fibre . Some pictures seem to be missing, but the text is there. @Oliver: if you can send me a .zip with the pictures I can upload it.
thank you, but I've already uploaded the html-pages to http://olk.github.io/libs/fiber/doc/html/
2013/12/18 Nat Goodspeed <nat@lindenlab.com>
Hi all,
The review of Boost.Fiber by Oliver Kowalke is scheduled from Monday, January 6th to January 12th.
----------------------------------------------------- About the library:
Boost.Fiber provides a framework for micro-/userland-threads (fibers) scheduled cooperatively. The API contains classes and functions to manage and synchronize fibers similar to Boost.Thread. Each fiber has its own stack.
A fiber can save the current execution state, including all registers and CPU flags, the instruction pointer, and the stack pointer and later restore this state. The idea is to have multiple execution paths running on a single thread using a sort of cooperative scheduling (versus threads, which are preemptively scheduled). The running fiber decides explicitly when it should yield to allow another fiber to run (context switching). Boost.Fiberinternally uses coroutines from Boost.Coroutine <http://ok73.funpic.de/boost/libs/coroutine/index.html>; the classes in this library manage, schedule and, when needed, synchronize those coroutines. A context switch between threads usually costs thousands of CPU cycles on x86, compared to a fiber switch with a few hundred cycles. A fiber can only run on a single thread at any point in time.
docs: http://ok73.funpic.de/boost/libs/fiber/doc/html/index.html<http://ok73.ok.funpic.de/boost/libs/coroutine/doc/html/> git: https://github.com/olk/boost-fiber src: http://ok73.ok.funpic.de/boost.fiber.zip<http://ok73.ok.funpic.de/boost.coroutine.zip>
---------------------------------------------------
Naturally, you need not wait until the review formally opens to start reviewing the Fiber library. Please always state in your review whether you think the library should be accepted as a Boost library!
Additionally please consider giving feedback on the following general topics:
- What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Nat Goodspeed Boost.Fiber Review Manager
the documentation is now available at http://olk.github.io/libs/fiber/doc/html/ too (no popup-windows)
Thanks for the doc! Is it possible to say when will the Fiber lib be givin the "ok!" to be used in a production environment? On 20 December 2013 15:19, Oliver Kowalke <oliver.kowalke@gmail.com> wrote:
2013/12/18 Nat Goodspeed <nat@lindenlab.com>
Hi all,
The review of Boost.Fiber by Oliver Kowalke is scheduled from Monday, January 6th to January 12th.
----------------------------------------------------- About the library:
Boost.Fiber provides a framework for micro-/userland-threads (fibers) scheduled cooperatively. The API contains classes and functions to manage and synchronize fibers similar to Boost.Thread. Each fiber has its own stack.
A fiber can save the current execution state, including all registers and CPU flags, the instruction pointer, and the stack pointer and later restore this state. The idea is to have multiple execution paths running on a single thread using a sort of cooperative scheduling (versus threads, which are preemptively scheduled). The running fiber decides explicitly when it should yield to allow another fiber to run (context switching). Boost.Fiberinternally uses coroutines from Boost.Coroutine <http://ok73.funpic.de/boost/libs/coroutine/index.html>; the classes in this library manage, schedule and, when needed, synchronize those coroutines. A context switch between threads usually costs thousands of CPU cycles on x86, compared to a fiber switch with a few hundred cycles. A fiber can only run on a single thread at any point in time.
docs: http://ok73.funpic.de/boost/libs/fiber/doc/html/index.html<http://ok73.ok.funpic.de/boost/libs/coroutine/doc/html/> git: https://github.com/olk/boost-fiber src: http://ok73.ok.funpic.de/boost.fiber.zip<http://ok73.ok.funpic.de/boost.coroutine.zip>
---------------------------------------------------
Naturally, you need not wait until the review formally opens to start reviewing the Fiber library. Please always state in your review whether you think the library should be accepted as a Boost library!
Additionally please consider giving feedback on the following general topics:
- What is your evaluation of the design? - What is your evaluation of the implementation? - What is your evaluation of the documentation? - What is your evaluation of the potential usefulness of the library? - Did you try to use the library? With what compiler? Did you have any problems? - How much effort did you put into your evaluation? A glance? A quick reading? In-depth study? - Are you knowledgeable about the problem domain? Nat Goodspeed Boost.Fiber Review Manager
the documentation is now available at http://olk.github.io/libs/fiber/doc/html/ too (no popup-windows)
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
-- Carlos Miguel Ferreira Researcher at Telecommunications Institute Aveiro - Portugal Work E-mail - cmf@av.it.pt Skype & GTalk -> carlosmf.pt@gmail.com LinkedIn -> http://www.linkedin.com/in/carlosmferreira
participants (6)
-
Bjorn Reese -
Carlos Ferreira -
Giovanni Piero Deretta -
Nat Goodspeed -
Oliver Kowalke -
Wouter van Ooijen