[pypy-commit] pypy.org extradoc: add stm donations
fijal
noreply at buildbot.pypy.org
Mon Mar 5 23:42:47 CET 2012
Author: Maciej Fijalkowski <fijall at gmail.com>
Branch: extradoc
Changeset: r337:0367b0d0cc4f
Date: 2012-03-05 14:41 -0800
http://bitbucket.org/pypy/pypy.org/changeset/0367b0d0cc4f/
Log: add stm donations
diff --git a/archive.html b/archive.html
--- a/archive.html
+++ b/archive.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/compat.html b/compat.html
--- a/compat.html
+++ b/compat.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/contact.html b/contact.html
--- a/contact.html
+++ b/contact.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/don1.html b/don1.html
--- a/don1.html
+++ b/don1.html
@@ -1,5 +1,6 @@
<ul>
<li>
+ <a href="#" onclick="stm_donate(); return false;">Donate towards STM in pypy</a><br/>
<a href="#" onclick="py3k_donate(); return false;"><b>Donate towards py3k in pypy</b></a><br/>
<a href="#" onclick="general_donate(); return false;">Donate towards general pypy progress</a><br/>
<a href="#" onclick="numpy_donate(); return false;">Donate towards NumPy in pypy</a><br/>
diff --git a/don2.html b/don2.html
--- a/don2.html
+++ b/don2.html
@@ -1,5 +1,6 @@
<ul>
<li>
+ <a href="#" onclick="stm_donate(); return false;">Donate towards STM in pypy</a><br/>
<a href="#" onclick="py3k_donate(); return false;">Donate towards py3k in pypy</a><br/>
<a href="#" onclick="general_donate(); return false;"><b>Donate towards general pypy progress</b></a><br/>
<a href="#" onclick="numpy_donate(); return false;">Donate towards NumPy in pypy</a><br/>
diff --git a/don3.html b/don3.html
--- a/don3.html
+++ b/don3.html
@@ -1,5 +1,6 @@
<ul>
<li>
+ <a href="#" onclick="stm_donate(); return false;">Donate towards STM in pypy</a><br/>
<a href="#" onclick="py3k_donate(); return false;">Donate towards py3k in pypy</a><br/>
<a href="#" onclick="general_donate(); return false;">Donate towards general pypy progress</a><br/>
<a href="#" onclick="numpy_donate(); return false;"><b>Donate towards NumPy in pypy</b></a><br/>
diff --git a/don4.html b/don4.html
new file mode 100644
--- /dev/null
+++ b/don4.html
@@ -0,0 +1,76 @@
+<ul>
+ <li>
+ <a href="#" onclick="stm_donate(); return false;">Donate towards STM in pypy</a><br/>
+ <a href="#" onclick="py3k_donate(); return false;">Donate towards py3k in pypy</a><br/>
+ <a href="#" onclick="general_donate(); return false;">Donate towards general pypy progress</a><br/>
+ <a href="#" onclick="numpy_donate(); return false;"><b>Donate towards NumPy in pypy</b></a><br/>
+ </li>
+ <li>
+<script>
+ $(function() {
+ $("#progressbar").progressbar({
+ value: 0.0
+ });
+ });
+</script>
+
+ $0 of $50400
+ <div id="progressbar">
+ </div>
+
+ </li>
+ <li>
+ <span id="donate_text">This donation will go towards supporting the Transactional Memory in PyPy <a href="tmdonate.html">Read proposal</a>
+ </li>
+ <li>
+ <li>
+ <div class="sidepic">
+ <form action="https://www.paypal.com/cgi-bin/webscr" method="post">
+ <input type="hidden" name="cmd" value="_s-xclick">
+ <input type="hidden" name="hosted_button_id" value="XU6QHLK6CZX6E">
+ <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_donateCC_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!">
+ <img alt="" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1">
+ </form>
+ </div>
+ </li>
+ <li>
+ <div class="sidepic">
+ <script type="text/javascript">
+ function validateAmount(amount){
+ if(amount.value.match( /^[0-9]+(\.([0-9]+))?$/)){
+ return true;
+ }else{
+ alert('You must enter a valid donation.');
+ amount.focus();
+ return false;
+ }
+ }
+ </script>
+ <form action="https://checkout.google.com/cws/v2/Donations/622836985124940/checkoutForm" id="BB_BuyButtonForm" method="post" name="BB_BuyButtonForm" onSubmit="return validateAmount(this.item_price_1)" target="_top">
+ <input name="item_name_1" type="hidden" value="Directed Donation for PyPy's Transactional Memory project"/>
+ <input name="item_description_1" type="hidden" value="A directed donation via Software Freedom Conservancy, Inc. for PyPy's Transactional Memory Project."/>
+ <input name="item_quantity_1" type="hidden" value="1"/>
+ <input name="item_currency_1" type="hidden" value="USD"/>
+ <input name="item_is_modifiable_1" type="hidden" value="true"/>
+ <input name="item_min_price_1" type="hidden" value="10.0"/>
+ <input name="item_max_price_1" type="hidden" value="25000.0"/>
+ <input name="_charset_" type="hidden" value="utf-8"/>
+ <table cellpadding="5" cellspacing="0" width="1%">
+ <tr>
+ <td align="right" nowrap="nowrap" width="1%">$ <input id="item_price_1" name="item_price_1" onfocus="this.style.color='black'; this.value='';" size="11" style="color:grey;" type="text" value="Enter Amount"/>
+ </td>
+ <td align="left" width="1%">
+ <input alt="Donate" src="https://checkout.google.com/buttons/donateNow.gif?merchant_id=622836985124940&w=115&h=50&style=white&variant=text&loc=en_US" type="image"/>
+ </td>
+ </tr>
+ </table>
+ </form>
+ </div>
+ </li>
+ <li>
+ <div class="sidepic">
+ <a id="main_download" href="download.html">Download PyPy</a>
+ </div>
+ </li>
+</ul>
+
diff --git a/download.html b/download.html
--- a/download.html
+++ b/download.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/features.html b/features.html
--- a/features.html
+++ b/features.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/howtohelp.html b/howtohelp.html
--- a/howtohelp.html
+++ b/howtohelp.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/index.html b/index.html
--- a/index.html
+++ b/index.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/js/script2.js b/js/script2.js
--- a/js/script2.js
+++ b/js/script2.js
@@ -5,6 +5,12 @@
});
}
+function stm_donate() {
+ $.get("don4.html#", function (html) {
+ $("#sidebar").html(html);
+ });
+}
+
function general_donate() {
$.get("don2.html#", function (html) {
$("#sidebar").html(html);
@@ -18,5 +24,5 @@
}
$(document).ready(function() {
- numpy_donate();
+ stm_donate();
});
\ No newline at end of file
diff --git a/numpydonate.html b/numpydonate.html
--- a/numpydonate.html
+++ b/numpydonate.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/people.html b/people.html
--- a/people.html
+++ b/people.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/performance.html b/performance.html
--- a/performance.html
+++ b/performance.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/py3donate.html b/py3donate.html
--- a/py3donate.html
+++ b/py3donate.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/source/_layouts/site.genshi b/source/_layouts/site.genshi
--- a/source/_layouts/site.genshi
+++ b/source/_layouts/site.genshi
@@ -15,6 +15,7 @@
('Contact', 'contact.html'),
('Py3k donations', 'py3donate.html'),
('NumPy donations', 'numpydonate.html'),
+ ('STM donations', 'tmdonate.html'),
],
}
diff --git a/source/tmdonate.txt b/source/tmdonate.txt
new file mode 100644
--- /dev/null
+++ b/source/tmdonate.txt
@@ -0,0 +1,389 @@
+---
+layout: page
+title: Call for donations - Transactional Memory in PyPy
+---
+
+====================
+Transactional Memory
+====================
+
+
+Introduction
+============
+
+In the presence of today's machines with multiple processors, Python
+progress is lagging behind: on any CPU-constrained program, developers
+have a difficult choice to make. They can use in-process solutions that
+do not offer multi-CPU usage. In this respect, the natural choice
+nowadays is to use Twisted or other event-based paradigms, or systems
+that hide events in the control flow, like Stackless; or alternatively,
+they can use the existing ``threading`` module, with its associated GIL
+and the complexities of real multi-threaded programming (locks,
+deadlocks, races, etc.), which make this solution less attractive. The
+big alternative is for them to rely on one of various multi-process
+solutions that are outside the scope of the core language; all of them
+in some way or another are hacks that require extra knowledge and time
+to use and that have an impact on the structure of the whole program.
+
+This proposal is about researching and implementing Transactional Memory
+in PyPy. This is a technique that recently came to the front of the
+multi-core scene. It promizes to offer multi-core CPU usage without
+requiring to fall back to the multi-process solutions described above,
+and also without using the ``threading`` module --- just as a small,
+local extension of the programming language that would be used only in
+the core of the event loops.
+
+(Jump directly to `What Python interface will I use?`_ for practical
+details.)
+
+
+In more details
+===============
+
+This is a call for financial help in researching and implementing a
+version of PyPy able to use multiple processors in a single process.
+This will give a GIL-less Python, i.e. a Python that runs without the
+infamous Global Interpreter Lock.
+
+The basic ideas to do it have been discussed on pypy-dev `[1]`__ `[2]`__
+and on a blog post `[3]`__.
+The goal is to adapt Transactional Memory --- currently only available
+as software, but `soon available as hardware`_ --- to the task of running
+sections of Python code in parallel on multiple processors, while giving
+the programmer the illusion of serial execution. It is called below
+"PyPy-TM".
+
+.. __: http://mail.python.org/pipermail/pypy-dev/2011-August/008153.html
+.. __: http://mail.python.org/pipermail/pypy-dev/2012-January/009034.html
+.. __: http://morepypy.blogspot.com/2012/01/transactional-memory-ii.html
+
+The main developer will be Armin Rigo.
+This is a "researchy" goal in the sense of us not being quite sure of
+the performance of the result. We currently estimate the one-year
+performance goal at 2x-to-5x slower than regular PyPy in fully serial
+applications. We feel confident that it can work, though, in the
+following sense: the performance of PyPy-TM running suited applications
+should scale linearly or close-to-linearly with the number of processors.
+This means that you just need a machine with at least 4 or 8 processors,
+which is already common today and will be even more so in one or two
+years.
+
+You will find below a sketch of the `work plan`_. If more money than
+requested is collected, then the excess will be entered into the general
+PyPy pot, used for example to finance sprint travel costs to students.
+
+**Note** For donations higher than $1,000, we can arrange for an invoice
+and a different payment method to avoid the high Paypal fees. Please
+contact pypy at sfconservancy.org if you want to know details on how
+to donate via other means.
+
+
+What is the Global Interpreter Lock?
+------------------------------------
+
+The GIL, or Global Interpreter Lock, is a single lock in both CPython
+and (so far) PyPy, that all threads must acquire in order to execute
+Python bytecodes. This means that so far, in Python, even when using
+threads we do not gain any benefit in term of multicore performance.
+
+
+What is Transactional Memory?
+-----------------------------
+
+`Transactional Memory`_ (TM) is a technique imported from databases: every
+time we want to do a change to the processors' main memory, we do it in
+a "transaction". Multiple transactions can be executed in parallel by
+multiple cores. When a transaction is complete, we try to commit it.
+This might either succeed, or (if another transaction committed
+incompatible changes) fail. If it fails, which is hopefully rare, we
+need to restart the transaction from scratch.
+
+.. _`Transactional Memory`: http://en.wikipedia.org/wiki/Transactional_memory
+
+
+Why hasn't the idea been implemented for CPython already?
+---------------------------------------------------------
+
+Because of the additional complexity required, and mostly, because of
+performance issues. There have been some experiments already with
+CPython on *Hardware* Transactional Memory:
+
+* `Riley and Zilles (2006)`__
+* `Tabba (2010)`__
+
+.. __: http://sabi.net/nriley/pubs/dls6-riley.pdf
+.. __: http://www.cs.auckland.ac.nz/~fuad/parpycan.pdf
+
+The motivation for using PyPy instead of CPython is the extra
+flexibility of the general approach, as well as the ability to utilize
+the JIT in order to remove part of the overhead that comes with
+*Software* Transactional Memory.
+
+
+A GIL-less Python is impossible.
+--------------------------------
+
+This is a classic criticism of research-oriented projects. We believe
+that the `work plan`_ plan below can make a serious impact on considering
+possible a GIL-less Python. We believe we can do it, but at the
+very least, even if this work generates a negative result, the negative
+result will document the challenges faced should someone else want to
+reattempt the idea in the future.
+
+Nevertheless other projects, such as Psyco (also by Armin) and PyPy
+itself, were called impossible before they were attempted, and have
+hitherto been very successful.
+
+
+Why do it with PyPy instead of CPython?
+---------------------------------------
+
+Because PyPy is designed to be open to this kind of research. This will
+require no work in the Python interpreter part of PyPy, and instead we
+can focus on e.g. the concurrent garbage collection and the JIT issues.
+`Riley and Zilles`__ have also experimented with Hardware Transactional
+Memory using PyPy. By contrast, for example, CPython is stuck with
+reference counting, which is known to be an issue for Transactional
+Memory (`Tabba`__ proposes to give up and use Boehm_, which is a bad
+idea in our experience, particularly because of scalability issues).
+
+.. __: http://sabi.net/nriley/pubs/dls6-riley.pdf
+.. __: http://www.cs.auckland.ac.nz/~fuad/parpycan.pdf
+.. _Boehm: http://www.hpl.hp.com/personal/Hans_Boehm/gc/
+
+
+What Python interface will I use?
+---------------------------------
+
+Previous attempts on Hardware
+Transactional Memory focused on parallelizing existing programs written
+using the ``thread`` or ``threading`` modules. However, as argued
+here__, this may not be the most practical way to achieve real
+multithreading; it seems that better alternatives would offer good
+scalability too. Notably, TM could benefit any event-based system that
+is written to dispatch events serially (Twisted-based, most GUI toolkit,
+Stackless, gevent, and so on). The events would internally be processed
+in parallel, while maintaining the illusion of serial execution, with
+all the corresponding benefits of safety. This should be possible with minimal
+changes to the event dispatchers. This approach has been described by the
+`Automatic Mutual Exclusion`_ work at Microsoft Research, but not been
+implemented anywhere (to the best of our knowledge).
+
+.. _`Automatic Mutual Exclusion`: http://research.microsoft.com/en-us/projects/ame/default.aspx
+
+Note that, yes, this gives you both sides of the coin: you keep using
+your non-thread-based program (without worrying about locks and their
+drawbacks like deadlocks, races, and friends), *and* your programs
+benefit from all your cores.
+
+.. __: http://mail.python.org/pipermail/pypy-dev/2012-January/009044.html
+
+In more details, a low-level built-in module will provide the basics to
+start transactions in parallel; but this module will be only used
+internally in a tweaked version of, say, a Twisted reactor. Using this
+reactor will be enough for your existing Twisted-based programs to
+actually run on multiple cores. You --- as a developer of the
+Twisted-based program --- have only to care about improving the
+parallelizability of your program (e.g. by splitting time-consuming
+transactions into several parts; the exact rules will be published in
+detail once they are known). But the point is that your program is
+always correct.
+
+
+Speed
+-----
+
+We estimate the one-year performance target to be 2x-to-5x slower than
+the performance of the regular PyPy in fully serial applications. (Of
+course, the regular PyPy will not disappear; for the foreseeable future,
+PyPy-TM will be an alternative executable.)
+
+The performance of PyPy-TM running suited applications should scale
+linearly or close-to-linearly with the number of processor. This means
+that in order to see the benefits, you just need a machine with at least
+4 or 8 processors --- which is already common today and will be even
+more so in one or two years.
+
+
+.. _`soon available as hardware`:
+
+Hardware Transactional Memory
+-----------------------------
+
+The performance of PyPy-TM running on Hardware Transactional Memory is
+unknown so far, but should ideally be close to the performance of a
+regular PyPy.
+
+In more details: This proposal is for work based entirely on *Software*
+Transactional Memory. However, in the future the ideas and most of the
+code should map directly to Hardware Transactional Memory (HTM). We
+expect HTM to reduce a lot the cost of some of the issues that we face,
+but not completely remove it. For example, `AMD's old proposal`_ was
+that there would be two ways to emit memory-referencing
+instructions: one that goes via the HTM mechanisms, and one (the regular
+one) which doesn't. Choosing the best one on a
+case-by-case basis in the JIT makes a difference in
+performance (although of course not as great as with Software
+Transactional Memory).
+
+`Intel's current proposal`_ on Haswell_ processors does not have this
+distinction, which means transactions are likely to quickly overflow the
+internal buffers. As a result, the first generation HTM-capable
+processors may not be suited for the approach described here. But
+this depends on details like the capacity of the hardware buffers that
+are still secret at this point.
+
+(Note also that HTM does not solve some of the issues for implementing
+Transactional Memory in CPython, notably the issue with reference
+counting. We will have to wait for a real CPython experiment before
+we can settle this question. Also, this would "just" remove the GIL
+but not offer a multi-core version of non-thread-based programs.)
+
+.. _`AMD's old proposal`: http://developer.amd.com/tools/ASF/Pages/default.aspx
+.. _`Intel's current proposal`: http://software.intel.com/en-us/avx/
+.. _Haswell: http://en.wikipedia.org/wiki/Haswell_%28microarchitecture%29
+
+
+Alternatives
+------------
+
+PyPy-TM will be slower than judicious usage of existing alternatives,
+based on multiple processes that communicate with each other in one way
+or another. The counter-argument is that TM is not only a cleaner
+solution: there are cases in which it is not doable to organize (or
+retrofit) an existing program into the particular format needed for the
+alternatives. In particular, small quickly-written programs don't need
+the additional baggage of cross-process communication, and large
+programs can sometimes be almost impossible to turn into multi-process
+versions. By constrast, we believe that TM can fit naturally into most
+programs, because it only requires local changes to some dispatcher; the
+rest of the program should work without changes.
+
+
+More readings
+-------------
+
+* `Original blog post`__
+* pypy-dev mails `[1]`__ `[2]`__
+* `The most recent blog post`__
+
+.. __: http://morepypy.blogspot.com/2011/08/we-need-software-transactional-memory.html
+.. __: http://mail.python.org/pipermail/pypy-dev/2011-August/008153.html
+.. __: http://mail.python.org/pipermail/pypy-dev/2012-January/009034.html
+.. __: http://morepypy.blogspot.com/2012/01/transactional-memory-ii.html
+
+
+Work plan
+=========
+
+This is an very rough estimate of the amount of work it would take to
+complete the steps for an experienced developer who is already familiar
+with the PyPy codebase. As this is a research proposal, we cannot
+guarantee the time estimates here, but we do agree to report regularly to
+the community, so our progress can be followed publicly.
+
+Paid work will be at $60/hour, but at least one developer who will work on
+the project --- Armin Rigo --- has committed to 2 hours
+of volunteer work per paid hour (so
+the total amount of money that we ask is divided by three). A 5% general
+donation will go to the `Software Freedom Conservancy`_ itself, the
+non-profit organization of which the PyPy project is a member and which
+manages all the issues related to donations, payments, and tax-exempt
+status.
+
+.. _`Software Freedom Conservancy`: http://sfconservancy.org/
+.. _rstm: http://www.cs.rochester.edu/research/synchronization/rstm/
+
+
+* **STM Library**:
+
+ This part covers adapting an existing STM library for PyPy. It is
+ already mostly done (based on rstm_), but additional tweaks may be
+ required.
+
+* **Basic tweaks of the translation process**:
+
+ This part covers tweaks needed during the translation process in
+ order to generate an STM-aware version of the RPython programs,
+ including PyPy itself. It is partly done, but not finished.
+ Estimate: 1 month.
+
+* **Garbage collection**:
+
+ We need a different garbage collector that is able to cope at least
+ with concurrent allocations. From there, improving the situation is
+ its own open-ended subproject: we can add for example various kinds of
+ parallel collection, synchronized or unsynchronized root tracing,
+ etc. Estimate for the basic part: 2 months. Estimate for the rest:
+ 4 extra months.
+
+* **User interface**:
+
+ This is the problem of designing and implementing some interface or
+ interfaces for the Python programmer. We put it in its own category
+ because of its "end-user" importance. Estimate: 2 months.
+
+* **JIT integration**:
+
+ The above would give us a (probably very slow) version of PyPy-TM.
+ This final part is to integrate it with the JIT compiler generator.
+ The main issue we foresee is integration with the new GC, detecting
+ with object flags or JIT optimizations which objects need
+ transactional memory status or not. We think that with enough such
+ optimizations we can seriously lower the overhead of PyPy-TM, maybe
+ down to 2x slower than a regular PyPy or better. Estimate: unknown;
+ at least 4 months.
+
+* **Longer term**:
+
+ In the longer term, we might need to refine the TM processing done
+ above, for example to better support I/O (e.g. we can queue the writes
+ done to a log file) or to add some special fine-grained support
+ (e.g. two transactions that each do ``samelist.append()`` do not need
+ to conflict in the simple case). This part is not included
+ in the estimates.
+
+Total: 5 months for the initial version; at least 8 additional months
+for the fast version. We will go with a total estimate of 15 months,
+corresponding to USD$151200. The amount sought by this fundraising
+campaign, considering the 2 volunteer hours per paid hour is thus USD$50400.
+
+
+Benefits of This Work to the Python Community and the General Public
+====================================================================
+
+Python has become one of the most popular dynamic programming languages in
+the world. Web developers, educators, and scientific programmers alike
+all value Python because Python code is often more readable and because
+Python often increases programmer productivity.
+
+Traditionally, languages like Python ran more slowly than static, compiled
+languages; Python developers chose to sacrifice execution speed for ease
+of programming. The PyPy project created a substantially improved Python
+language implementation, including a fast Just-in-time (JIT) compiler.
+The increased execution speed that PyPy provides has attracted many users,
+who now find their Python code runs up to four times faster under PyPy
+than under the reference implementation written in C.
+
+However, in the presence of today's machines with multiple processors,
+Python progress lags behind. The issue has been described in the
+introduction: developers that really need to use multiple CPUs are
+constrained to select and use one of the multi-process solutions that
+are all in some way or another hacks requiring extra knowledge and
+efforts to use. The focus of the work described in this proposal is to
+offer an alternative in the core of the Python language --- an
+alternative that can naturally integrate with the rest of the program.
+This alternative will be implemented in PyPy.
+
+PyPy's developers make all PyPy software available to the public without
+charge, under PyPy's Open Source copyright license, the permissive MIT
+License. PyPy's license assures that PyPy is equally available to
+everyone freely on terms that allow both non-commercial and commercial
+activity. This license allows for academics, for-profit software
+developers, volunteers and enthusiasts alike to collaborate together to
+make a better Python implementation for everyone.
+
+PyPy-TM will be available under the same license. Being licensed freely
+to the general public means that opportunities to use, improve and learn
+about how Transactional Memory works itself will be generally available
+to everyone.
diff --git a/sponsor.html b/sponsor.html
--- a/sponsor.html
+++ b/sponsor.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/success.html b/success.html
--- a/success.html
+++ b/success.html
@@ -38,7 +38,7 @@
</div>
<div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
<hr class="clear-left" />
- <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a></div>
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
<hr class="clear" />
</div>
<div id="content">
diff --git a/tmdonate.html b/tmdonate.html
new file mode 100644
--- /dev/null
+++ b/tmdonate.html
@@ -0,0 +1,355 @@
+<!DOCTYPE html>
+<html>
+<head>
+ <title>PyPy :: Call for donations - Transactional Memory in PyPy</title>
+ <meta http-equiv="content-language" content="en" />
+ <meta http-equiv="content-type" content="text/html; charset=utf-8" />
+ <meta name="author" content="PyPy Team" />
+ <meta name="description" content="PyPy" />
+ <meta name="copyright" content="MIT" />
+ <meta name="document-rating" content="general" />
+ <link rel="stylesheet" type="text/css" media="screen" title="default" href="css/site.css" />
+ <link rel="alternate" type="application/rss+xml" title="RSS Feed for PyPy" href="http://feeds.feedburner.com/PyPyStatusBlog" />
+ <link rel="stylesheet" type="text/css" href="css/jquery-ui-1.8.14.custom.css" />
+ <script type="text/javascript" src="http://use.typekit.com/hdt8sni.js"></script>
+ <script type="text/javascript">try{Typekit.load();}catch(e){}</script>
+ <script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.4.2/jquery.min.js"></script>
+ <script type="text/javascript" src="js/jquery-ui-1.8.14.custom.min.js"></script>
+ <script type="text/javascript" src="js/detect.js"></script>
+ <script type="text/javascript" src="js/script2.js?bust=1"></script>
+</head>
+<body>
+<script type="text/javascript">
+ var _gaq = [['_setAccount', 'UA-7778406-3'], ['_trackPageview']];
+ if (document.location.protocol !== 'file:') {
+ (function() {
+ var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
+ ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
+ (document.getElementsByTagName('head')[0] || document.getElementsByTagName('body')[0]).appendChild(ga);
+ })();
+ }
+</script>
+<div id="body-outer"><div id="body-inner"><div id="body" class="clearfix">
+<div id="header">
+ <div id="menu-follow">
+ <div><a href="http://search.twitter.com/search?q=%23pypy" title="Follow the conversation on Twitter"><img src="http://static.ampify.it/icon.twitter.gif" alt="Follow the conversation on Twitter" width="14px" height="14px" /></a></div>
+ <div><a href="https://bitbucket.org/pypy/pypy"><img src="http://www.selenic.com/hg-logo/logo-droplets-25.png" width="14px" height="14px" /></a></div>
+ <div><a href="http://feeds.feedburner.com/PyPyStatusBlog" title="Subscribe to the RSS Feed"><img src="http://static.ampify.it/icon.rss.png" alt="Subscribe to the RSS Feed" width="14px" height="14px" /></a></div>
+ </div>
+ <div id="logo"><a href="http://pypy.org"><img src="image/pypy-logo.png" alt="PyPy" height="110px" /></a></div>
+ <hr class="clear-left" />
+ <div id="menu-sub"><a href="index.html">Home</a><span class="menu-sub-sep"> | </span><a href="features.html">Features</a><span class="menu-sub-sep"> | </span><a href="download.html">Download</a><span class="menu-sub-sep"> | </span><a href="compat.html">Compatibility</a><span class="menu-sub-sep"> | </span><a href="performance.html">Performance</a><span class="menu-sub-sep"> | </span><a href="http://doc.pypy.org">Dev Documentation</a><span class="menu-sub-sep"> | </span><a href="http://morepypy.blogspot.com">Blog</a><span class="menu-sub-sep"> | </span><a href="people.html">People</a><span class="menu-sub-sep"> | </span><a href="contact.html">Contact</a><span class="menu-sub-sep"> | </span><a href="py3donate.html">Py3k donations</a><span class="menu-sub-sep"> | </span><a href="numpydonate.html">NumPy donations</a><span class="menu-sub-sep"> | </span><a href="tmdonate.html">STM donations</a></div>
+ <hr class="clear" />
+</div>
+<div id="content">
+<div>
+<div id="main">
+<h1 class="title">Call for donations - Transactional Memory in PyPy</h1>
+<div class="section" id="introduction">
+<h1>Introduction</h1>
+<p>In the presence of today's machines with multiple processors, Python
+progress is lagging behind: on any CPU-constrained program, developers
+have a difficult choice to make. They can use in-process solutions that
+do not offer multi-CPU usage. In this respect, the natural choice
+nowadays is to use Twisted or other event-based paradigms, or systems
+that hide events in the control flow, like Stackless; or alternatively,
+they can use the existing <tt class="docutils literal">threading</tt> module, with its associated GIL
+and the complexities of real multi-threaded programming (locks,
+deadlocks, races, etc.), which make this solution less attractive. The
+big alternative is for them to rely on one of various multi-process
+solutions that are outside the scope of the core language; all of them
+in some way or another are hacks that require extra knowledge and time
+to use and that have an impact on the structure of the whole program.</p>
+<p>This proposal is about researching and implementing Transactional Memory
+in PyPy. This is a technique that recently came to the front of the
+multi-core scene. It promizes to offer multi-core CPU usage without
+requiring to fall back to the multi-process solutions described above,
+and also without using the <tt class="docutils literal">threading</tt> module – just as a small,
+local extension of the programming language that would be used only in
+the core of the event loops.</p>
+<p>(Jump directly to <a class="reference internal" href="#what-python-interface-will-i-use">What Python interface will I use?</a> for practical
+details.)</p>
+</div>
+<div class="section" id="in-more-details">
+<h1>In more details</h1>
+<p>This is a call for financial help in researching and implementing a
+version of PyPy able to use multiple processors in a single process.
+This will give a GIL-less Python, i.e. a Python that runs without the
+infamous Global Interpreter Lock.</p>
+<p>The basic ideas to do it have been discussed on pypy-dev <a class="reference external" href="http://mail.python.org/pipermail/pypy-dev/2011-August/008153.html">[1]</a> <a class="reference external" href="http://mail.python.org/pipermail/pypy-dev/2012-January/009034.html">[2]</a>
+and on a blog post <a class="reference external" href="http://morepypy.blogspot.com/2012/01/transactional-memory-ii.html">[3]</a>.
+The goal is to adapt Transactional Memory – currently only available
+as software, but <a class="reference internal" href="#soon-available-as-hardware">soon available as hardware</a> – to the task of running
+sections of Python code in parallel on multiple processors, while giving
+the programmer the illusion of serial execution. It is called below
+“PyPy-TM”.</p>
+<p>The main developer will be Armin Rigo.
+This is a “researchy” goal in the sense of us not being quite sure of
+the performance of the result. We currently estimate the one-year
+performance goal at 2x-to-5x slower than regular PyPy in fully serial
+applications. We feel confident that it can work, though, in the
+following sense: the performance of PyPy-TM running suited applications
+should scale linearly or close-to-linearly with the number of processors.
+This means that you just need a machine with at least 4 or 8 processors,
+which is already common today and will be even more so in one or two
+years.</p>
+<p>You will find below a sketch of the <a class="reference internal" href="#work-plan">work plan</a>. If more money than
+requested is collected, then the excess will be entered into the general
+PyPy pot, used for example to finance sprint travel costs to students.</p>
+<p><strong>Note</strong> For donations higher than $1,000, we can arrange for an invoice
+and a different payment method to avoid the high Paypal fees. Please
+contact pypy at sfconservancy.org if you want to know details on how
+to donate via other means.</p>
+<div class="section" id="what-is-the-global-interpreter-lock">
+<h2>What is the Global Interpreter Lock?</h2>
+<p>The GIL, or Global Interpreter Lock, is a single lock in both CPython
+and (so far) PyPy, that all threads must acquire in order to execute
+Python bytecodes. This means that so far, in Python, even when using
+threads we do not gain any benefit in term of multicore performance.</p>
+</div>
+<div class="section" id="what-is-transactional-memory">
+<h2>What is Transactional Memory?</h2>
+<p><a class="reference external" href="http://en.wikipedia.org/wiki/Transactional_memory">Transactional Memory</a> ™ is a technique imported from databases: every
+time we want to do a change to the processors' main memory, we do it in
+a “transaction”. Multiple transactions can be executed in parallel by
+multiple cores. When a transaction is complete, we try to commit it.
+This might either succeed, or (if another transaction committed
+incompatible changes) fail. If it fails, which is hopefully rare, we
+need to restart the transaction from scratch.</p>
+</div>
+<div class="section" id="why-hasn-t-the-idea-been-implemented-for-cpython-already">
+<h2>Why hasn't the idea been implemented for CPython already?</h2>
+<p>Because of the additional complexity required, and mostly, because of
+performance issues. There have been some experiments already with
+CPython on <em>Hardware</em> Transactional Memory:</p>
+<ul class="simple">
+<li><a class="reference external" href="http://sabi.net/nriley/pubs/dls6-riley.pdf">Riley and Zilles (2006)</a></li>
+<li><a class="reference external" href="http://www.cs.auckland.ac.nz/~fuad/parpycan.pdf">Tabba (2010)</a></li>
+</ul>
+<p>The motivation for using PyPy instead of CPython is the extra
+flexibility of the general approach, as well as the ability to utilize
+the JIT in order to remove part of the overhead that comes with
+<em>Software</em> Transactional Memory.</p>
+</div>
+<div class="section" id="a-gil-less-python-is-impossible">
+<h2>A GIL-less Python is impossible.</h2>
+<p>This is a classic criticism of research-oriented projects. We believe
+that the <a class="reference internal" href="#work-plan">work plan</a> plan below can make a serious impact on considering
+possible a GIL-less Python. We believe we can do it, but at the
+very least, even if this work generates a negative result, the negative
+result will document the challenges faced should someone else want to
+reattempt the idea in the future.</p>
+<p>Nevertheless other projects, such as Psyco (also by Armin) and PyPy
+itself, were called impossible before they were attempted, and have
+hitherto been very successful.</p>
+</div>
+<div class="section" id="why-do-it-with-pypy-instead-of-cpython">
+<h2>Why do it with PyPy instead of CPython?</h2>
+<p>Because PyPy is designed to be open to this kind of research. This will
+require no work in the Python interpreter part of PyPy, and instead we
+can focus on e.g. the concurrent garbage collection and the JIT issues.
+<a class="reference external" href="http://sabi.net/nriley/pubs/dls6-riley.pdf">Riley and Zilles</a> have also experimented with Hardware Transactional
+Memory using PyPy. By contrast, for example, CPython is stuck with
+reference counting, which is known to be an issue for Transactional
+Memory (<a class="reference external" href="http://www.cs.auckland.ac.nz/~fuad/parpycan.pdf">Tabba</a> proposes to give up and use <a class="reference external" href="http://www.hpl.hp.com/personal/Hans_Boehm/gc/">Boehm</a>, which is a bad
+idea in our experience, particularly because of scalability issues).</p>
+</div>
+<div class="section" id="what-python-interface-will-i-use">
+<h2>What Python interface will I use?</h2>
+<p>Previous attempts on Hardware
+Transactional Memory focused on parallelizing existing programs written
+using the <tt class="docutils literal">thread</tt> or <tt class="docutils literal">threading</tt> modules. However, as argued
+<a class="reference external" href="http://mail.python.org/pipermail/pypy-dev/2012-January/009044.html">here</a>, this may not be the most practical way to achieve real
+multithreading; it seems that better alternatives would offer good
+scalability too. Notably, TM could benefit any event-based system that
+is written to dispatch events serially (Twisted-based, most GUI toolkit,
+Stackless, gevent, and so on). The events would internally be processed
+in parallel, while maintaining the illusion of serial execution, with
+all the corresponding benefits of safety. This should be possible with minimal
+changes to the event dispatchers. This approach has been described by the
+<a class="reference external" href="http://research.microsoft.com/en-us/projects/ame/default.aspx">Automatic Mutual Exclusion</a> work at Microsoft Research, but not been
+implemented anywhere (to the best of our knowledge).</p>
+<p>Note that, yes, this gives you both sides of the coin: you keep using
+your non-thread-based program (without worrying about locks and their
+drawbacks like deadlocks, races, and friends), <em>and</em> your programs
+benefit from all your cores.</p>
+<p>In more details, a low-level built-in module will provide the basics to
+start transactions in parallel; but this module will be only used
+internally in a tweaked version of, say, a Twisted reactor. Using this
+reactor will be enough for your existing Twisted-based programs to
+actually run on multiple cores. You – as a developer of the
+Twisted-based program – have only to care about improving the
+parallelizability of your program (e.g. by splitting time-consuming
+transactions into several parts; the exact rules will be published in
+detail once they are known). But the point is that your program is
+always correct.</p>
+</div>
+<div class="section" id="speed">
+<h2>Speed</h2>
+<p>We estimate the one-year performance target to be 2x-to-5x slower than
+the performance of the regular PyPy in fully serial applications. (Of
+course, the regular PyPy will not disappear; for the foreseeable future,
+PyPy-TM will be an alternative executable.)</p>
+<p>The performance of PyPy-TM running suited applications should scale
+linearly or close-to-linearly with the number of processor. This means
+that in order to see the benefits, you just need a machine with at least
+4 or 8 processors – which is already common today and will be even
+more so in one or two years.</p>
+</div>
+<div class="section" id="hardware-transactional-memory">
+<span id="soon-available-as-hardware"></span><h2>Hardware Transactional Memory</h2>
+<p>The performance of PyPy-TM running on Hardware Transactional Memory is
+unknown so far, but should ideally be close to the performance of a
+regular PyPy.</p>
+<p>In more details: This proposal is for work based entirely on <em>Software</em>
+Transactional Memory. However, in the future the ideas and most of the
+code should map directly to Hardware Transactional Memory (HTM). We
+expect HTM to reduce a lot the cost of some of the issues that we face,
+but not completely remove it. For example, <a class="reference external" href="http://developer.amd.com/tools/ASF/Pages/default.aspx">AMD's old proposal</a> was
+that there would be two ways to emit memory-referencing
+instructions: one that goes via the HTM mechanisms, and one (the regular
+one) which doesn't. Choosing the best one on a
+case-by-case basis in the JIT makes a difference in
+performance (although of course not as great as with Software
+Transactional Memory).</p>
+<p><a class="reference external" href="http://software.intel.com/en-us/avx/">Intel's current proposal</a> on <a class="reference external" href="http://en.wikipedia.org/wiki/Haswell_%28microarchitecture%29">Haswell</a> processors does not have this
+distinction, which means transactions are likely to quickly overflow the
+internal buffers. As a result, the first generation HTM-capable
+processors may not be suited for the approach described here. But
+this depends on details like the capacity of the hardware buffers that
+are still secret at this point.</p>
+<p>(Note also that HTM does not solve some of the issues for implementing
+Transactional Memory in CPython, notably the issue with reference
+counting. We will have to wait for a real CPython experiment before
+we can settle this question. Also, this would “just” remove the GIL
+but not offer a multi-core version of non-thread-based programs.)</p>
+</div>
+<div class="section" id="alternatives">
+<h2>Alternatives</h2>
+<p>PyPy-TM will be slower than judicious usage of existing alternatives,
+based on multiple processes that communicate with each other in one way
+or another. The counter-argument is that TM is not only a cleaner
+solution: there are cases in which it is not doable to organize (or
+retrofit) an existing program into the particular format needed for the
+alternatives. In particular, small quickly-written programs don't need
+the additional baggage of cross-process communication, and large
+programs can sometimes be almost impossible to turn into multi-process
+versions. By constrast, we believe that TM can fit naturally into most
+programs, because it only requires local changes to some dispatcher; the
+rest of the program should work without changes.</p>
+</div>
+<div class="section" id="more-readings">
+<h2>More readings</h2>
+<ul class="simple">
+<li><a class="reference external" href="http://morepypy.blogspot.com/2011/08/we-need-software-transactional-memory.html">Original blog post</a></li>
+<li>pypy-dev mails <a class="reference external" href="http://mail.python.org/pipermail/pypy-dev/2011-August/008153.html">[1]</a> <a class="reference external" href="http://mail.python.org/pipermail/pypy-dev/2012-January/009034.html">[2]</a></li>
+<li><a class="reference external" href="http://morepypy.blogspot.com/2012/01/transactional-memory-ii.html">The most recent blog post</a></li>
+</ul>
+</div>
+</div>
+<div class="section" id="work-plan">
+<h1>Work plan</h1>
+<p>This is an very rough estimate of the amount of work it would take to
+complete the steps for an experienced developer who is already familiar
+with the PyPy codebase. As this is a research proposal, we cannot
+guarantee the time estimates here, but we do agree to report regularly to
+the community, so our progress can be followed publicly.</p>
+<p>Paid work will be at $60/hour, but at least one developer who will work on
+the project – Armin Rigo – has committed to 2 hours
+of volunteer work per paid hour (so
+the total amount of money that we ask is divided by three). A 5% general
+donation will go to the <a class="reference external" href="http://sfconservancy.org/">Software Freedom Conservancy</a> itself, the
+non-profit organization of which the PyPy project is a member and which
+manages all the issues related to donations, payments, and tax-exempt
+status.</p>
+<ul>
+<li><p class="first"><strong>STM Library</strong>:</p>
+<p>This part covers adapting an existing STM library for PyPy. It is
+already mostly done (based on <a class="reference external" href="http://www.cs.rochester.edu/research/synchronization/rstm/">rstm</a>), but additional tweaks may be
+required.</p>
+</li>
+<li><p class="first"><strong>Basic tweaks of the translation process</strong>:</p>
+<p>This part covers tweaks needed during the translation process in
+order to generate an STM-aware version of the RPython programs,
+including PyPy itself. It is partly done, but not finished.
+Estimate: 1 month.</p>
+</li>
+<li><p class="first"><strong>Garbage collection</strong>:</p>
+<p>We need a different garbage collector that is able to cope at least
+with concurrent allocations. From there, improving the situation is
+its own open-ended subproject: we can add for example various kinds of
+parallel collection, synchronized or unsynchronized root tracing,
+etc. Estimate for the basic part: 2 months. Estimate for the rest:
+4 extra months.</p>
+</li>
+<li><p class="first"><strong>User interface</strong>:</p>
+<p>This is the problem of designing and implementing some interface or
+interfaces for the Python programmer. We put it in its own category
+because of its “end-user” importance. Estimate: 2 months.</p>
+</li>
+<li><p class="first"><strong>JIT integration</strong>:</p>
+<p>The above would give us a (probably very slow) version of PyPy-TM.
+This final part is to integrate it with the JIT compiler generator.
+The main issue we foresee is integration with the new GC, detecting
+with object flags or JIT optimizations which objects need
+transactional memory status or not. We think that with enough such
+optimizations we can seriously lower the overhead of PyPy-TM, maybe
+down to 2x slower than a regular PyPy or better. Estimate: unknown;
+at least 4 months.</p>
+</li>
+<li><p class="first"><strong>Longer term</strong>:</p>
+<p>In the longer term, we might need to refine the TM processing done
+above, for example to better support I/O (e.g. we can queue the writes
+done to a log file) or to add some special fine-grained support
+(e.g. two transactions that each do <tt class="docutils literal">samelist.append()</tt> do not need
+to conflict in the simple case). This part is not included
+in the estimates.</p>
+</li>
+</ul>
+<p>Total: 5 months for the initial version; at least 8 additional months
+for the fast version. We will go with a total estimate of 15 months,
+corresponding to USD$151200. The amount sought by this fundraising
+campaign, considering the 2 volunteer hours per paid hour is thus USD$50400.</p>
+</div>
+<div class="section" id="benefits-of-this-work-to-the-python-community-and-the-general-public">
+<h1>Benefits of This Work to the Python Community and the General Public</h1>
+<p>Python has become one of the most popular dynamic programming languages in
+the world. Web developers, educators, and scientific programmers alike
+all value Python because Python code is often more readable and because
+Python often increases programmer productivity.</p>
+<p>Traditionally, languages like Python ran more slowly than static, compiled
+languages; Python developers chose to sacrifice execution speed for ease
+of programming. The PyPy project created a substantially improved Python
+language implementation, including a fast Just-in-time (JIT) compiler.
+The increased execution speed that PyPy provides has attracted many users,
+who now find their Python code runs up to four times faster under PyPy
+than under the reference implementation written in C.</p>
+<p>However, in the presence of today's machines with multiple processors,
+Python progress lags behind. The issue has been described in the
+introduction: developers that really need to use multiple CPUs are
+constrained to select and use one of the multi-process solutions that
+are all in some way or another hacks requiring extra knowledge and
+efforts to use. The focus of the work described in this proposal is to
+offer an alternative in the core of the Python language – an
+alternative that can naturally integrate with the rest of the program.
+This alternative will be implemented in PyPy.</p>
+<p>PyPy's developers make all PyPy software available to the public without
+charge, under PyPy's Open Source copyright license, the permissive MIT
+License. PyPy's license assures that PyPy is equally available to
+everyone freely on terms that allow both non-commercial and commercial
+activity. This license allows for academics, for-profit software
+developers, volunteers and enthusiasts alike to collaborate together to
+make a better Python implementation for everyone.</p>
+<p>PyPy-TM will be available under the same license. Being licensed freely
+to the general public means that opportunities to use, improve and learn
+about how Transactional Memory works itself will be generally available
+to everyone.</p>
+</div>
+</div>
+<div id="sidebar">
+</div>
+</div>
+</div>
+</div></div></div>
+</body>
+</html>
\ No newline at end of file
More information about the pypy-commit
mailing list