<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: New TTY Layer moves into FreeBSD</title>
	<atom:link href="http://www.evilcoder.org/2008/08/20/nieuwe-tty-layer-in-freebsd/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.evilcoder.org/2008/08/20/nieuwe-tty-layer-in-freebsd/</link>
	<description>My contribution to the World</description>
	<lastBuildDate>Sat, 13 Mar 2010 09:51:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: New TTY Layer moves into FreeBSD &#124; BSD News</title>
		<link>http://www.evilcoder.org/2008/08/20/nieuwe-tty-layer-in-freebsd/comment-page-1/#comment-1291</link>
		<dc:creator>New TTY Layer moves into FreeBSD &#124; BSD News</dc:creator>
		<pubDate>Tue, 16 Mar 2010 20:11:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.evilcoder.org/?p=955#comment-1291</guid>
		<description>[...] Today is a big day, for me, for Ed Schouten and for FreeBSD (And it’s consumers ofcourse). Why? Ed Schouten today integrated his MultiProcessorSafe (MPSAFE) implementation of the TTY Layer for FreeBSD. From the beginning that I heared about the project, Ed and I had been in contact, both working at the same company (Snow B.V.), we flew to Canada together (Facilitated and sponsored by Snow B.V.), visited eachother, been in contact for ages (or at least it feels like ages, which is a positive point in this case). Ed also gratuated in the meantime by working on this TTY layer. So a lot of good things had been evolved because of this! [...]</description>
		<content:encoded><![CDATA[<p>[...] Today is a big day, for me, for Ed Schouten and for FreeBSD (And it’s consumers ofcourse). Why? Ed Schouten today integrated his MultiProcessorSafe (MPSAFE) implementation of the TTY Layer for FreeBSD. From the beginning that I heared about the project, Ed and I had been in contact, both working at the same company (Snow B.V.), we flew to Canada together (Facilitated and sponsored by Snow B.V.), visited eachother, been in contact for ages (or at least it feels like ages, which is a positive point in this case). Ed also gratuated in the meantime by working on this TTY layer. So a lot of good things had been evolved because of this! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FreeBSD Status Report: April bis Juni 2008 &#124; F!XMBR</title>
		<link>http://www.evilcoder.org/2008/08/20/nieuwe-tty-layer-in-freebsd/comment-page-1/#comment-1290</link>
		<dc:creator>FreeBSD Status Report: April bis Juni 2008 &#124; F!XMBR</dc:creator>
		<pubDate>Tue, 16 Mar 2010 17:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.evilcoder.org/?p=955#comment-1290</guid>
		<description>[...] Noch nicht dort erw&#228;hnt aber just eingeflossen: der neue TTY-Layer in Current. Giant-free sorgt dieser somit ebenso f&#252;r eine v&#246;llig neue Dimension der Arbeit in FreeBSD. In what&#8217;s cooking kann jeder FreeBSD-Interessierte dar&#252;ber hinaus regelm&#228;&#223;ig den aktuellen Wasserstand in der Entwicklung nachlesen. [...]</description>
		<content:encoded><![CDATA[<p>[...] Noch nicht dort erw&auml;hnt aber just eingeflossen: der neue TTY-Layer in Current. Giant-free sorgt dieser somit ebenso f&uuml;r eine v&ouml;llig neue Dimension der Arbeit in FreeBSD. In what&#8217;s cooking kann jeder FreeBSD-Interessierte dar&uuml;ber hinaus regelm&auml;&szlig;ig den aktuellen Wasserstand in der Entwicklung nachlesen. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Remko</title>
		<link>http://www.evilcoder.org/2008/08/20/nieuwe-tty-layer-in-freebsd/comment-page-1/#comment-1289</link>
		<dc:creator>Remko</dc:creator>
		<pubDate>Tue, 16 Mar 2010 14:18:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.evilcoder.org/?p=955#comment-1289</guid>
		<description>Well, the processing part was GIANT lock free. But several subsystems still use the GIANT lock (just boot your computer and you&#039;ll see those various systems). By having the TTY-layer GIANT-lock free, we can make the modules that use this (and are still under GIANT locking) MPsafe at some point. I see this as important infrastructure that we can continue to build upon.

And not only that, the new code is more modular and makes new things possible (hopefully); so perhaps something like ethernet-tty&#039;s or other fancy things ;-)</description>
		<content:encoded><![CDATA[<p>Well, the processing part was GIANT lock free. But several subsystems still use the GIANT lock (just boot your computer and you&#8217;ll see those various systems). By having the TTY-layer GIANT-lock free, we can make the modules that use this (and are still under GIANT locking) MPsafe at some point. I see this as important infrastructure that we can continue to build upon.</p>
<p>And not only that, the new code is more modular and makes new things possible (hopefully); so perhaps something like ethernet-tty&#8217;s or other fancy things <img src='http://www.evilcoder.org/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: heavensrevenge</title>
		<link>http://www.evilcoder.org/2008/08/20/nieuwe-tty-layer-in-freebsd/comment-page-1/#comment-1288</link>
		<dc:creator>heavensrevenge</dc:creator>
		<pubDate>Tue, 16 Mar 2010 14:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.evilcoder.org/?p=955#comment-1288</guid>
		<description>well, i thought we got rid of that GIANT lock with the ULE scheduler... but hey, anything helping remove an implicit or assumed global lock that will limit performance, and force serialized code, will be great.  Cant wait for FreeBSD to be able to run on a cloud/grid/farm/cluster with a reasonable amount of robustness :)</description>
		<content:encoded><![CDATA[<p>well, i thought we got rid of that GIANT lock with the ULE scheduler&#8230; but hey, anything helping remove an implicit or assumed global lock that will limit performance, and force serialized code, will be great.  Cant wait for FreeBSD to be able to run on a cloud/grid/farm/cluster with a reasonable amount of robustness <img src='http://www.evilcoder.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New TTY Layer moves into FreeBSD &#124; FreeBSD - the unknown Giant</title>
		<link>http://www.evilcoder.org/2008/08/20/nieuwe-tty-layer-in-freebsd/comment-page-1/#comment-1287</link>
		<dc:creator>New TTY Layer moves into FreeBSD &#124; FreeBSD - the unknown Giant</dc:creator>
		<pubDate>Tue, 16 Mar 2010 13:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.evilcoder.org/?p=955#comment-1287</guid>
		<description>[...] Read further&#8230;       &#171; How to resize ZFS in FreeNAS [...]</description>
		<content:encoded><![CDATA[<p>[...] Read further&#8230;       &laquo; How to resize ZFS in FreeNAS [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Kosela</title>
		<link>http://www.evilcoder.org/2008/08/20/nieuwe-tty-layer-in-freebsd/comment-page-1/#comment-1286</link>
		<dc:creator>Andy Kosela</dc:creator>
		<pubDate>Tue, 16 Mar 2010 12:19:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.evilcoder.org/?p=955#comment-1286</guid>
		<description>Thanks :)</description>
		<content:encoded><![CDATA[<p>Thanks <img src='http://www.evilcoder.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
