<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>funded project | FreeBSD Foundation</title>
	<atom:link href="https://staging.freebsdfoundation.org/tag/funded-project/feed/" rel="self" type="application/rss+xml" />
	<link>https://staging.freebsdfoundation.org</link>
	<description>A non-profit organization dedicated to supporting and building the FreeBSD Project</description>
	<lastBuildDate>Tue, 02 Jan 2024 16:35:51 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://staging.freebsdfoundation.org/wp-content/uploads/2015/12/favicon.png</url>
	<title>funded project | FreeBSD Foundation</title>
	<link>https://staging.freebsdfoundation.org</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>2023 in Review: Continuous Integration and Workflow Improvement</title>
		<link>https://staging.freebsdfoundation.org/blog/continuous-integration-and-workflow-improvement/</link>
		
		<dc:creator><![CDATA[Anne Dickison]]></dc:creator>
		<pubDate>Fri, 29 Dec 2023 22:41:42 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Cloud Support]]></category>
		<category><![CDATA[Continuous Integration]]></category>
		<category><![CDATA[funded project]]></category>
		<guid isPermaLink="false">https://freebsdfoundation.org/?p=13578</guid>

					<description><![CDATA[<p>As part of our continued support of the FreeBSD Project, we have a full-time staff member dedicated to improving the Project’s continuous integration system and the test infrastructure. In 2023, we added more testing jobs for ARM64 architectures like testing with Kernel Address Sanitizer and building test for non-standard compilers like GCC 12 and 13. [&#8230;]</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/continuous-integration-and-workflow-improvement/">2023 in Review: Continuous Integration and Workflow Improvement</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-core-paragraph">
<p>As part of our continued support of the FreeBSD Project, we have a full-time staff member dedicated to improving the Project’s continuous integration system and the test infrastructure. In 2023, we added more testing jobs for ARM64 architectures like testing with Kernel Address Sanitizer and building test for non-standard compilers like GCC 12 and 13.</p>
</section>

<section class="block block-core-paragraph">
<p>We have also made great progress running the workflow working group, designing and implementing systems to support the pull-request based workflow. Pre-commit CI is on the horizon as well.</p>
</section>

<section class="block block-core-paragraph">
<p>We worked with a summer intern to&nbsp;update the &#8220;Tinderbox View&#8221; (<a href="https://tinderbox.freebsd.org/">https://tinderbox.freebsd.org</a>) of the CI result dashboard.&nbsp;It now provides more details of the test results and the possible breakage point.</p>
</section>

<section class="block block-core-paragraph">
<p></p>
</section>

<section class="block block-core-heading">
<h2 class="wp-block-heading">Cloud support</h2>
</section>

<section class="block block-core-paragraph">
<p>The Foundation also supports our full-time staff member’s efforts to work with the engineers from Microsoft to help them implement support for new features in Azure and provide more FreeBSD features in Azure. This includes ARM64 VM support, Gen2 VM support and ZFS images provided. All these changes are included in 14.0-RELEASE and published to the Azure Marketplace.</p>
</section>

<section class="block block-core-paragraph">
<p>As always, the Foundation’s support of CI and Microsoft Cloud environments is only possible because of your investment in FreeBSD. If you have not yet done so, please consider supporting FreeBSD before the year-end.</p>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/continuous-integration-and-workflow-improvement/">2023 in Review: Continuous Integration and Workflow Improvement</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Security, Performance, and Interoperability; Introducing FreeBSD 14</title>
		<link>https://staging.freebsdfoundation.org/blog/security-performance-and-interoperability-introducing-freebsd-14/</link>
		
		<dc:creator><![CDATA[Anne Dickison]]></dc:creator>
		<pubDate>Thu, 14 Dec 2023 20:43:55 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[freebsd]]></category>
		<category><![CDATA[funded project]]></category>
		<guid isPermaLink="false">https://freebsdfoundation.org/?p=13480</guid>

					<description><![CDATA[<p>The FreeBSD community is proud to herald the release of FreeBSD 14. FreeBSD 14 brings further security and performance enhancements, along with extended support and interoperability.</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/security-performance-and-interoperability-introducing-freebsd-14/">Security, Performance, and Interoperability; Introducing FreeBSD 14</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-core-paragraph">
<p></p>
</section>

<section class="block block-core-paragraph">
<p></p>
</section>

<section class="block block-core-paragraph">
<p>The FreeBSD community is proud to herald the release of FreeBSD 14. FreeBSD 14 represents the 82nd release in the history of one of the world’s first open source projects, and contains over two and a half years of development work since the launch of the previous release. FreeBSD is the engine behind some of the world’s most well-known and widely used systems and brands including Sony Playstation, NetApp, Juniper, NetScaler, Netflix, and Netgate. With support until at least November 30th, 2028 for the FreeBSD 14.x series of releases, FreeBSD 14 continues FreeBSD’s legacy of creating an exceptionally stable, secure, and performance-oriented operating system. FreeBSD 14 brings further security and performance enhancements, along with extended support and interoperability. In this blog, we&#8217;ll take a look at these key themes to outline what’s new in FreeBSD 14, and more importantly, why it matters.</p>
</section>

<section class="block block-core-paragraph">
<p></p>
</section>

<section class="block block-core-heading">
<h2 class="wp-block-heading"><strong>Security</strong></h2>
</section>

<section class="block block-core-paragraph">
<p>FreeBSD has a long legacy of being a secure and stable open source operating system. FreeBSD’s developers continue to work on, and prioritize, security with the intention of creating the most secure version of FreeBSD possible. FreeBSD 14 provides increased security in multiple areas, including Capsicum sandboxing, authentication, the removal of unnecessary services, and more. It is important to note that some security updates announced for the release of FreeBSD 14 have been incorporated into existing 13.x releases in order to ensure their enterprise-level stability and readiness before their formal introduction in FreeBSD 14.</p>
</section>

<section class="block block-core-paragraph">
<p>Capsicum is a lightweight operating system capability and sandboxing framework that was initially developed by University of Cambridge with grants from Google, DARPA, and The FreeBSD Foundation. Capsicum stands out as a framework that allows developers to create programs that operate within a safe sandbox environment that is separate and isolated from the rest of their environment. The prototype for Capsicum was developed during the FreeBSD 8.x releases and Capsicum has continued to see improvements in FreeBSD ever since. For example, FreeBSD 14 brings <a href="https://man.freebsd.org/cgi/man.cgi?query=sockstat&amp;sektion=1&amp;format=html">sockstat(1)</a> to Capscum sandboxing. Sockstat(1) is a versatile utility that displays open sockets within FreeBSD. The sockstat(1) utility can be used for a wide range of use cases, including &#8211; but certainly not limited to &#8211; troubleshooting.</p>
</section>

<section class="block block-core-paragraph">
<p>FreeBSD 14 also provides further measures to prevent return-oriented programming attacks. A return-oriented-programming attack (ROP) is a technique that allows attackers to execute code in their target system by gaining control of a system’s call stack. Mature open source projects, like FreeBSD, have numerous developers throughout the world, making further iteration inherent. FreeBSD 14 represents a continuation of existing security measures in this area by enabling position independent executable and address space layout randomization by default for 64-bit architectures.</p>
</section>

<section class="block block-core-paragraph">
<p>Lastly, FreeBSD 14 provides updates in cryptography and email, making FreeBSD 14 ideal for highly regulated industries and government. FreeBSD 14 includes support for FIDO/U2F hardware authenticators. FIDO/U2F is an open authentication standard, overseen by the FIDO Alliance, that was created by Google, Yubico, and NXP Semiconductors, with the vision of making a secure public key cryptography system. Aside from support for FIDO/U2F, FreeBSD 14 introduces a more secure, lightweight, and performance-driven default mail transport agent in <a href="https://man.freebsd.org/cgi/man.cgi?query=dma&amp;sektion=8&amp;format=html">Dragonfly Mail Agent</a>. Dragonfly Mail Agent provides the maximum security possible in the smallest footprint for users who would like to set their own balance between security, performance, and load-management.</p>
</section>

<section class="block block-core-paragraph">
<p></p>
</section>

<section class="block block-core-heading">
<h2 class="wp-block-heading"><strong>Performance</strong></h2>
</section>

<section class="block block-core-paragraph">
<p>FreeBSD is known for many other things besides security, and high-performance is one of them. In fact, Netflix has done <a href="https://www.youtube.com/watch?v=36qZYL5RlgY">numerous talks </a>about the kind of cutting-edge networking throughput they’re seeing. But it’s not just Netflix that benefits from FreeBSD’s high-performance capabilities. <a href="https://www.youtube.com/watch?v=u0mG-wSKzn8&amp;feature=youtu.be">Companies like Simpro</a> <a href="https://www.youtube.com/watch?v=7bzNAKxAeMQ">and Deepstack</a> have given talks about how they have benefitted from FreeBSD’s performance capabilities. FreeBSD 14 provides additional performance enhancements that can lead to less downtime and helps FreeBSD take the lead in the world of serverless computing.</p>
</section>

<section class="block block-core-paragraph">
<p>FreeBSD 14 now reboots even faster than before. To be precise, <a href="https://www.theregister.com/2023/08/29/freebsd_boots_in_25ms/">FreeBSD can now boot in only 25 milliseconds</a>. This massive performance improvement makes FreeBSD 14 an ideal choice for microVMs. FreeBSD 14 also lays the groundwork for further compatibility with <a href="https://firecracker-microvm.github.io/">Firecracker Virtual Machine Monitor</a>. Although much of the groundwork laid in FreeBSD 14 to optimize for serverless computing is in the background and not in user experience, a faster reboot time is noticeable, and further work is ongoing in the area of serverless computing. Stay tuned!</p>
</section>

<section class="block block-core-heading">
<h2 class="wp-block-heading"><strong>Support and Interoperability</strong></h2>
</section>

<section class="block block-core-paragraph">
<p>FreeBSD 14 focuses heavily on support and interoperability with other systems including Linux and major cloud providers. Let’s face it, a hallmark of open source technology is the freedom and ability to choose software depending on what’s right for a user&#8217;s specific situation and FreeBSD is adding to that hallmark with FreeBSD 14.</p>
</section>

<section class="block block-core-paragraph">
<p>New efforts to enhance interoperability with Linux represent an interesting shift in direction for FreeBSD. FreeBSD 14 makes it easier for users to port applications and programs from Linux to FreeBSD, or vice versa. In this area, a number of utilities have been added to FreeBSD 14, including an <a href="https://man.freebsd.org/cgi/man.cgi?query=nproc&amp;sektion=1&amp;format=html">nproc(1)</a> utility, compatible with the Linux program of the same name, native<a href="https://man.freebsd.org/cgi/man.cgi?query=timerfd&amp;sektion=2&amp;format=html"> timerfd(2)</a> facility to enable porting of Linux programs that use timerfd, and a <a href="https://man.freebsd.org/cgi/man.cgi?query=netlink&amp;sektion=4&amp;format=html">netlink(4)</a> utility for further compatibility with Linux.&nbsp;</p>
</section>

<section class="block block-core-paragraph">
<p>Lastly in the theme of support and interoperability, FreeBSD 14 includes support for servers with greater CPU space on amd64 and arm64, up to 1024 cores, making FreeBSD an ideal choice for high-performance computing scenarios where systems are running large data-heavy applications. FreeBSD 14 provides further support for users of major cloud providers such as Microsoft Azure, Amazon Web Services, and Google Cloud. FreeBSD brings optimized networking support for Google Cloud and Microsoft Azure, ensuring that all three top cloud providers now have enhanced networking support in FreeBSD. FreeBSD 14 also brings a superior filesystem in the form of ZFS for use on Amazon Web Services and Microsoft Azure. FreeBSD users with arm64 and amd64 architectures are also now supported on all Azure VM types.&nbsp;</p>
</section>

<section class="block block-core-paragraph">
<p></p>
</section>

<section class="block block-core-heading">
<h2 class="wp-block-heading"><strong>In Summary</strong></h2>
</section>

<section class="block block-core-paragraph">
<p>Altogether, FreeBSD 14 includes countless new features supported by The FreeBSD Foundation, and represents a strong step forward for the FreeBSD Project. The release of FreeBSD 14 includes both iterative improvements, like support for OpenSSL 3.0.12, and innovations like an astoundingly fast reboot time along with further optimization for a serverless future. If you’re not currently familiar with FreeBSD and you’re interested in serverless computing, high-performance computing, or even a stable and secure operating system, now might be a good time to start looking into FreeBSD. To get started, visit <a href="https://www.freebsd.org/">FreeBSD.org</a> or <a href="https://www.freebsd.org/where/#download-rel140">Download FreeBSD 14</a>.</p>
</section>

<section class="block block-core-paragraph">
<p><br></p>
</section>

<section class="block block-core-gallery">
<figure class="wp-block-gallery aligncenter has-nested-images columns-default is-cropped wp-block-gallery-1 is-layout-flex wp-block-gallery-is-layout-flex"><section class="block block-core-image">
<figure class="wp-block-image size-large"><img decoding="async" width="300" height="156" data-id="13486" src="https://staging.freebsdfoundation.org/wp-content/uploads/2023/12/FreeBSD_Logo_linkedin-1.png" alt="" class="wp-image-13486"/></figure>
</section></figure>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/security-performance-and-interoperability-introducing-freebsd-14/">Security, Performance, and Interoperability; Introducing FreeBSD 14</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>New Funded Project: Improved IPv6 Support</title>
		<link>https://staging.freebsdfoundation.org/blog/new-funded-project-improved-ipv6-support/</link>
		
		<dc:creator><![CDATA[Dru Lavigne]]></dc:creator>
		<pubDate>Wed, 13 Apr 2011 13:37:54 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[funded project]]></category>
		<category><![CDATA[ipv6]]></category>
		<guid isPermaLink="false">https://www.freebsdfoundation.org/?p=1207</guid>

					<description><![CDATA[<p>The FreeBSD Foundation is pleased to announce that it has awarded Bjoern Zeeb a grant to improve the maturity of IPv6 support in FreeBSD and PC-BSD. This project is jointly sponsored with iXsystems. FreeBSD&#8217;s KAME-based reference implementation of IPv6 first appeared in FreeBSD 4.0, and can be found in a broad range of FreeBSD-derived commercial [&#8230;]</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/new-funded-project-improved-ipv6-support/">New Funded Project: Improved IPv6 Support</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-classic-editor">
<p>The FreeBSD Foundation is pleased to announce that it has awarded Bjoern Zeeb a grant to improve the maturity of IPv6 support in FreeBSD and PC-BSD. This project is jointly sponsored with iXsystems.</p>
<p>FreeBSD&#8217;s KAME-based reference implementation of IPv6 first appeared in FreeBSD 4.0, and can be found in a broad range of FreeBSD-derived commercial products. To date, IPv6 has been an optionally configured feature present in the default FreeBSD kernel; however, IPv6 configuration has implied configuration of IPv4. With much &#8220;IPv6-ready&#8221; application software relying on dual-stack behavior, broken IPv6 applications go unnoticed. Adding support for an IPv6 kernel without IPv4 will make FreeBSD and PC-BSD an ideal test and development platform for both open source and proprietary IPv6-aware application software.</p>
<p>&#8220;Narrowing down the code base to not rely on legacy IP will help us to identify OS and application components requiring improvement to work well in an IPv6 environment. This project will help to ensure a bright IPv6 future, as FreeBSD is used throughout the Internet: root name servers, storage appliances, routers, firewalls, TVs, desktop and mobile systems, and many of the world&#8217;s busiest web sites,&#8221; said Mr. Zeeb. FreeBSD Foundation director and FreeBSD core team member Robert Watson described the project as critical to the future of FreeBSD, &#8220;Bjoern&#8217;s work will not only improve the maturity of our IPv6 implementation, but also motivate improvement of applications used in million of deployed FreeBSD and FreeBSD-derived systems.&#8221; The project will also improve the quality and performance of FreeBSD&#8217;s IPv6 stack.</p>
<p>Bjoern Zeeb is a consultant based in Germany and has been an active FreeBSD committer since 2004. He is currently also a member of the FreeBSD Security and Release Engineering teams, and was recently awarded the Itojun Service Award for his work on IPv6 in FreeBSD.</p>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/new-funded-project-improved-ipv6-support/">New Funded Project: Improved IPv6 Support</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Summary of Five New TCP Congestion Control Algorithms Project</title>
		<link>https://staging.freebsdfoundation.org/blog/summary-of-five-new-tcp-congestion-control-algorithms-project/</link>
		
		<dc:creator><![CDATA[Dru Lavigne]]></dc:creator>
		<pubDate>Tue, 08 Mar 2011 04:55:27 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[funded project]]></category>
		<category><![CDATA[TCP]]></category>
		<guid isPermaLink="false">https://www.freebsdfoundation.org/?p=1244</guid>

					<description><![CDATA[<p>Grenville Armitage has provided a summary of the completed TCP Congestion Control Algorithms project: Background TCP is a crucial part of any modern operating system. FreeBSD&#8217;s standard &#8220;NewReno&#8221; congestion control (CC) is not able to fully utilize the high capacity links available today. A range of newer CC algorithms have emerged (and continue to emerge) [&#8230;]</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/summary-of-five-new-tcp-congestion-control-algorithms-project/">Summary of Five New TCP Congestion Control Algorithms Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-classic-editor">
<p>Grenville Armitage has provided a summary of the completed TCP Congestion Control Algorithms project:</p>
<h3>Background</h3>
<p>TCP is a crucial part of any modern operating system. FreeBSD&#8217;s standard &#8220;NewReno&#8221; congestion control (CC) is not able to fully utilize the high capacity links available today. A range of newer CC algorithms have emerged (and continue to emerge) from the networking research community over the past 15+ years. These include traditional loss-based algorithms (where packet losses indicate network congestion) and delay-based algorithms (where changes in Round Trip Time, RTT, are used to infer network congestion).</p>
<p>However, to date FreeBSD&#8217;s TCP stack has not had an easy-to-use mechanism for introducing new CC algorithms. In recent years the Centre for Advanced Internet Architectures (CAIA) at Swinburne University of Technology has (with the support of the Cisco University Research Program Fund at Community Foundation Silicon Valley) been developing a range of extensions to the FreeBSD TCP stack. These included a modular framework for adding new CC algorithms and new modular implementations of the existing NewReno algorithm, four other algorithms from the literature (H-TCP, CUBIC, Vegas and HD) and a novel algorithm developed at CAIA (CHD). In mid-2010 the FreeBSD Foundation funded CAIA to complete, tidy up and commit a number of these key enhancements to the FreeBSD TCP stack.</p>
<h3>Delivered</h3>
<p>Our project, &#8220;Five New TCP Congestion Control Algorithms for FreeBSD&#8221;, has delivered the following enhancements to FreeBSD&#8217;s TCP stack:</p>
<ul>
<li>Modular congestion control framework.</li>
<li>Khelp (Kernel Helper) and Hhook (Helper Hook) frameworks.</li>
<li>Basic Khelp/Hhook (Kernel help/hook) integration with the TCP stack.</li>
<li>ERTT (Enhanced Round Trip Time) Khelp module for delay-based TCP algorithms.</li>
<li>Modularised implementations of NewReno, CUBIC and HTCP loss-based TCP CC algorithms.</li>
<li>Modularised implementations of Vegas, &#8220;HD&#8221; and &#8220;CHD&#8221; delay-based TCP CC algorithms.</li>
<li><a href="https://staging.freebsdfoundation.org/wp-content/uploads/2015/12/CAIA-TR-110228A.pdf" target="_blank" rel="">Technical report</a> comparing the computational overhead associated with TCP before and after integrating the new frameworks and modularised NewReno algorithm</li>
</ul>
<h3>Benefits</h3>
<p>Each congestion control algorithm is implemented as a loadable kernel module. Algorithms can be selected to suit the application/network characteristics and requirements of the host&#8217;s installation. The modular CC framework also makes it much easier for developers to implement new algorithms, allowing FreeBSD&#8217;s TCP to be at the forefront of advancements in this area, while still maintaining the stability of its network stack.</p>
<p>CUBIC and HTCP are variants of TCP that provide significant performance improvements (relative to NewReno) over high bandwidth, high latency paths. Vegas, HD, and CHD utilise RTT fluctuations to provide a more timely indication of network congestion &#8212; by not forcing network queues to overflow, delay-based CC algorithms can help to keep queuing delays low along a network path. CHD is also tolerant of packet losses that are unrelated to congestion (such as can occur over wireless links).</p>
<p>In addition, the Khelp/Hhook frameworks provide useful kernel infrastructure which are not specific to the TCP stack and we anticipate they will be used elsewhere in the kernel in the future to provide other unrelated enhancements to FreeBSD.</p>
<h3>Participants</h3>
<p>Code development, testing, and documentation: David Hayes and Lawrence Stewart</p>
<p>Editorial review of code and documentation: Rui Paulo and Bjoern Zeeb</p>
<p>Project supervision: Grenville Armitage</p>
<p>Project URL: <a title="http://caia.swin.edu.au/freebsd/5cc/" href="http://caia.swin.edu.au/freebsd/5cc/" target="_blank">http://caia.swin.edu.au/freebsd/5cc/</a></p>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/summary-of-five-new-tcp-congestion-control-algorithms-project/">Summary of Five New TCP Congestion Control Algorithms Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Feed-Forward Clock Synchronization Algorithms Project</title>
		<link>https://staging.freebsdfoundation.org/blog/feed-forward-clock-synchronization-algorithms-project/</link>
		
		<dc:creator><![CDATA[Dru Lavigne]]></dc:creator>
		<pubDate>Tue, 21 Dec 2010 09:09:22 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[funded project]]></category>
		<category><![CDATA[synchronization]]></category>
		<guid isPermaLink="false">https://www.freebsdfoundation.org/?p=242</guid>

					<description><![CDATA[<p>The FreeBSD Foundation is pleased to announce that Julien Ridoux and Darryl Veitch at the University of Melbourne have been awarded a grant to implement support of feed-forward clock synchronization algorithms. The Network Time Protocol (NTP) is widely used for synchronization over the network and the ntpd daemon is the current reference synchronization algorithm. The [&#8230;]</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/feed-forward-clock-synchronization-algorithms-project/">Feed-Forward Clock Synchronization Algorithms Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-classic-editor">
<p>The FreeBSD Foundation is pleased to announce that Julien Ridoux and Darryl Veitch at the University of Melbourne have been awarded a grant to implement support of feed-forward clock synchronization algorithms.</p>
<p>The Network Time Protocol (NTP) is widely used for synchronization over the network and the ntpd daemon is the current reference synchronization algorithm. The system clock in FreeBSD is currently designed with ntpd in mind, leading to strong feedback coupling between the kernel and the synchronization daemon.</p>
<p>The <a href="http://www.cubinlab.ee.unimelb.edu.au/radclock/" target="_blank">RADclock</a> is an example of an alternative class of synchronization algorithms based on feed-forward principles. This project will provide the core support for feed-forward algorithms, so that alternatives to ntpd can be developed and tested. The central motivation for this is the strong potential of such approaches for highly robust and accurate synchronization.</p>
<p>Beyond this, virtualization is one of the next major challenges faced by time keeping systems. The current feedback synchronization model is complex and introduces its own dynamics, an approach that is not suited to the requirements of virtualization. Feed-forward based synchronization offers a cleaner and simpler approach, which is capable of providing accurate time keeping over live migration of virtual machines.</p>
<p>This project will conclude in March 2011.</p>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/feed-forward-clock-synchronization-algorithms-project/">Feed-Forward Clock Synchronization Algorithms Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Five new TCP Congestion Control Algorithms Project</title>
		<link>https://staging.freebsdfoundation.org/blog/five-new-tcp-congestion-control-algorithms-project/</link>
		
		<dc:creator><![CDATA[Dru Lavigne]]></dc:creator>
		<pubDate>Sat, 04 Dec 2010 05:35:53 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[funded project]]></category>
		<category><![CDATA[TCP]]></category>
		<guid isPermaLink="false">https://www.freebsdfoundation.org/?p=250</guid>

					<description><![CDATA[<p>The FreeBSD Foundation is pleased to announce that Swinburne University&#8217;s Technology&#8217;s Centre for Advanced Internet Architectures has been awarded a grant to implement five new TCP congestion control algorithms in FreeBSD. Correctly functioning congestion control (CC) is crucial to the efficient operation of the Internet and IP networks in general. CC dynamically balances a flow&#8217;s [&#8230;]</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/five-new-tcp-congestion-control-algorithms-project/">Five new TCP Congestion Control Algorithms Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-classic-editor">
<p>The FreeBSD Foundation is pleased to announce that Swinburne University&#8217;s Technology&#8217;s Centre for Advanced Internet Architectures has been awarded a grant to implement five new TCP congestion control algorithms in FreeBSD.</p>
<p>Correctly functioning congestion control (CC) is crucial to the efficient operation of the Internet and IP networks in general. CC dynamically balances a flow&#8217;s throughput against the inferred impact on the network, lowering throughput to protect the network as required.</p>
<p>The FreeBSD operating system&#8217;s TCP stack currently utilizes the defacto standard NewReno loss-based CC algorithm, which has known problems coping with many aspects of modern data networks like lossy or large bandwidth/delay paths. There is significant and ongoing work both in the research community and industry to address CC related problems, with a particular focus on TCP because of its ubiquitous deployment and use.</p>
<p>Swinburne University of Technology&#8217;s ongoing work with FreeBSD&#8217;s TCP stack and congestion control implementation has progressively matured. This project aims to refine their prototypes and integrate them into FreeBSD.</p>
<p>The project will conclude in January 2011.</p>
<h3>Addendum:</h3>
<p>The five protocols are:</p>
<ul>
<li><a href="http://tools.ietf.org/id/draft-leith-tcp-htcp-06.txt" target="_blank">H-TCP</a> for high bandwidth-delay product paths</li>
<li><a href="http://tools.ietf.org/id/draft-rhee-tcp-cubic-00.txt" target="_blank">CUBIC</a> for fast long-distance networks</li>
<li><a href="http://www.cs.arizona.edu/projects/protocols/" target="_blank">Vegas</a> for end to end congestion avoidance</li>
<li>and 2 new algorithms <a href="http://caia.swin.edu.au/urp/newtcp/tools.html" target="_blank">Hamilton Delay and CAIA-Hamilton Delay</a></li>
</ul>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/five-new-tcp-congestion-control-algorithms-project/">Five new TCP Congestion Control Algorithms Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Update on DAHDI Project</title>
		<link>https://staging.freebsdfoundation.org/blog/update-on-dahdi-project/</link>
		
		<dc:creator><![CDATA[Dru Lavigne]]></dc:creator>
		<pubDate>Mon, 18 Oct 2010 06:10:19 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[dahdi]]></category>
		<category><![CDATA[funded project]]></category>
		<guid isPermaLink="false">https://www.freebsdfoundation.org/?p=270</guid>

					<description><![CDATA[<p>Max Khon has completed the DAHDI Project and provides the following report: I am pleased to announce the completion of the DAHDI/FreeBSD project. DAHDI (Digium/Asterisk Hardware Device Interface) is an open-source device driver framework and a set of HW drivers for E1/T1, ISDN digital and FXO/FXS analog cards. The main goal of this funded project [&#8230;]</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/update-on-dahdi-project/">Update on DAHDI Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-classic-editor">
<p>Max Khon has completed the DAHDI Project and provides the following report:</p>
<p>I am pleased to announce the completion of the DAHDI/FreeBSD project.</p>
<p><a href="http://www.asterisk.org/dahdi/" target="_blank">DAHDI</a> (Digium/Asterisk Hardware Device Interface) is an open-source device driver framework and a set of HW drivers for E1/T1, ISDN digital and FXO/FXS analog cards.</p>
<p>The main goal of this funded project was to make it possible to use FreeBSD as a base system for software PBX solutions.</p>
<p>Currently, most of the DAHDI bits have been ported, including the DAHDI framework itself, HW drivers, TDMoE drivers, drivers for software and HW echo cancellation (Octasic, VPMADT032) and HW transcoding (TC400B). The project is hosted in the <a href="http://svn.digium.com/svn/dahdi/freebsd/" target="_blank">official DAHDI SVN repository</a>.</p>
<p><a href="http://www.freshports.org/misc/dahdi/" target="_blank">Misc/dahdi</a> in the FreeBSD ports collection now contains the most recent bits of DAHDI/FreeBSD and also some stuff that is not available in DAHDI/FreeBSD SVN due to licensing and copyright restrictions. These include the OSLEC echo canceller and the experimental zaphfc driver.</p>
<p>I will continue periodic merges from DAHDI/Linux SVN on a regular basis and roll out new DAHDI/FreeBSD releases. These will most likely be synchronized with DAHDI/Linux releases.</p>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/update-on-dahdi-project/">Update on DAHDI Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Update on FreeBSD Jail Based Virtualization Project</title>
		<link>https://staging.freebsdfoundation.org/blog/update-on-freebsd-jail-based-virtualization-project/</link>
		
		<dc:creator><![CDATA[Dru Lavigne]]></dc:creator>
		<pubDate>Thu, 26 Aug 2010 05:54:10 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[funded project]]></category>
		<category><![CDATA[jails]]></category>
		<guid isPermaLink="false">https://www.freebsdfoundation.org/?p=357</guid>

					<description><![CDATA[<p>Bjoern Zeeb has provided a summary regarding the completion of the funded portion of the FreeBSD Jail Based Virtualization Project: I am happy to report that the funded parts of the FreeBSD Jail Based Virtualization project are completed. Some of the results have been shipping with 8.1-RELEASE while others are ready to be merged to [&#8230;]</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/update-on-freebsd-jail-based-virtualization-project/">Update on FreeBSD Jail Based Virtualization Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-classic-editor">
<p>Bjoern Zeeb has provided a summary regarding the completion of the funded portion of the FreeBSD Jail Based Virtualization Project:</p>
<p>I am happy to report that the funded parts of the FreeBSD Jail Based Virtualization project are completed. Some of the results have been shipping with 8.1-RELEASE while others are ready to be merged to HEAD.</p>
<p>Jails have been the well known operating system level virtualization technique in FreeBSD for over a decade. The import of Marko Zec&#8217;s network stack virtualization has introduced a new way for abstracting subsystems. As part of this project, the abstraction framework has been generalized. Together with Jamie Gritton&#8217;s flexible jail configuration syscalls, this will provide the infrastructure for, and will ease the virtualization of, further subsystems without much code duplication. The next subsystems to be virtualized will likely be SYSV/Posix IPC to help, for example, PostgreSQL users. This will probably be followed by the process namespace.</p>
<p>Along with the framework, debugging facilities, such as the interactive kernel debugger, have been enhanced so that every new subsystem will be able to immediately make use of these improvements without modifying a single line of code. Libjail and jls can now work on core dumps and netstat is able to query individual live network stacks attached to jails.</p>
<p>For the virtual network stack, work was focused on network stack teardown, a concept introduced with the network stack virtualization. The primary goal was to prototype a shutdown of the (virtual) network stacks from top to bottom, which means letting interfaces go last rather than first and still being able to cleanly shutdown TCP connections. Good progress was made, but a lot of code over the last two decades was never written in a way to be cleanly stopped. Work on this will have to continue, along with virtualizing the remaining network subsystems to allow long term stability and a leak and panic free shutdown. As a side effect, users of non-virtualized network stacks will also benefit, as other general network stack problems are identified and fixed along the way.</p>
<p>I am happy to see more early adopters, former OpenSolaris users, and people contributing code or reporting problems and would like to encourage people to further support this project.</p>
<p>My special thanks go the FreeBSD Foundation and CK Software GmbH for having sponsored this project, as well as to John Baldwin and Philip Paeps for helping with review and excellent suggestions.</p>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/update-on-freebsd-jail-based-virtualization-project/">Update on FreeBSD Jail Based Virtualization Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>SIFTR Committed</title>
		<link>https://staging.freebsdfoundation.org/blog/siftr-committed/</link>
		
		<dc:creator><![CDATA[Dru Lavigne]]></dc:creator>
		<pubDate>Thu, 15 Jul 2010 05:07:08 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[funded project]]></category>
		<category><![CDATA[siftr]]></category>
		<guid isPermaLink="false">https://www.freebsdfoundation.org/?p=416</guid>

					<description><![CDATA[<p>On July 3, Lawrence Stewart committed SIFTR (Statistical Information For TCP Research) to HEAD. SIFTR was part of the Improvements to the FreeBSD TCP Stack project that the Foundation funded last year. SIFTR is a kernel module that logs a range of statistics on active TCP connections to a log file. It provides the ability [&#8230;]</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/siftr-committed/">SIFTR Committed</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-classic-editor">
<p>On July 3, Lawrence Stewart <a href="http://svn.freebsd.org/viewvc/base?view=revision&amp;revision=209662" target="_blank">committed</a> SIFTR (Statistical Information For TCP Research) to HEAD. SIFTR was part of the Improvements to the FreeBSD TCP Stack project that the Foundation funded last year. SIFTR is a kernel module that logs a range of statistics on active TCP connections to a log file. It provides the ability to make highly granular measurements of TCP connection state, aimed at system administrators, developers and researchers.</p>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/siftr-committed/">SIFTR Committed</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Resource Containers Project</title>
		<link>https://staging.freebsdfoundation.org/blog/resource-containers-project/</link>
		
		<dc:creator><![CDATA[Dru Lavigne]]></dc:creator>
		<pubDate>Fri, 02 Jul 2010 07:40:26 +0000</pubDate>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[funded project]]></category>
		<category><![CDATA[jails]]></category>
		<category><![CDATA[resource containers]]></category>
		<guid isPermaLink="false">https://www.freebsdfoundation.org/?p=419</guid>

					<description><![CDATA[<p>We are pleased to announce that Edward Tomasz Napierala has been awarded a grant to implement resource containers and a simple per-jail resource limits mechanism. Unlike Solaris zones, the current implementation of FreeBSD Jails does not provide per-jail resource limits. As a result, users are often forced to replace jails with other virtualization mechanisms. The [&#8230;]</p>
<p>The post <a href="https://staging.freebsdfoundation.org/blog/resource-containers-project/">Resource Containers Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></description>
										<content:encoded><![CDATA[<section class="block block-classic-editor">
<p>We are pleased to announce that Edward Tomasz Napierala has been awarded a grant to implement resource containers and a simple per-jail resource limits mechanism.</p>
<p>Unlike Solaris zones, the current implementation of FreeBSD Jails does not provide per-jail resource limits. As a result, users are often forced to replace jails with other virtualization mechanisms. The goal of this project is to create a single, unified framework for controlling resource utilisation, and to use that framework to implement per-jail resource limits. In the future, the same framework might be used to implement more sophisticated resource controls, such as Hierarchical Resource Limits, or to implement mechanisms similar to <a href="http://www.redbooks.ibm.com/abstracts/sg245977.html" target="_blank">AIX WLM</a>. It could also be used to provide precise resource usage accounting for administrative or billing purposes.</p>
<p>&#8220;It&#8217;s great that the Foundation decided to fund this project&#8221;, Edward noted. &#8220;It will make jail-based virtualization a much better choice in many scenarios, for example for Virtual Private Server providers.&#8221;</p>
<p>This project will be completed December, 2010.</p>
</section><p>The post <a href="https://staging.freebsdfoundation.org/blog/resource-containers-project/">Resource Containers Project</a> first appeared on <a href="https://staging.freebsdfoundation.org">FreeBSD Foundation</a>.</p>]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
