<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Andrew and Zeus,<br>
<br>
I have written a replacement for the nameserver a couple of days
ago. However, over time additional functionality has been added to
chips to write implementations for posixcompat: A capability storage
and a distributed semaphore API. The error Zeus is seeing right now
seems related to the capability storage since shmget/shmat is using
this piece of code. I have discussed this with Adrian a bit today
and we're currently not sure if these APIs should remain in chips or
if I should transfer these over to the new service (which would be a
hack as the new service builds upon the SKB and the SKB does not
(yet) support storage for capabilities).<br>
In addition, because the ECLiPSe CLP engine (used by the SKB) uses
some inline x86 assembler we still need chips for non-x86
architectures at the moment. Since we can't get completely rid of
chips yet I made a patch that should fix the send handlers.<br>
<br>
@Zeus: I could not reproduce your bug on my machine but the error
should be fairly straight-forward to fix. Feedback is appreciated if
this works for you.<br>
<br>
Gerd<br>
<br>
<br>
On 02/16/2012 05:18 PM, Baumann Andrew wrote:
<blockquote
cite="mid:CB50AAD779D31B4C8B0D1D3866C291AC03D04716@MBX21.d.ethz.ch"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 14 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi
Zeus,<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This
is an implementation bug in chips: it doesn’t handle the
TX_BUSY error (and gets away with it, because most clients
use chips only as an RPC service). It would be possible to
fix that by queuing up the sends, as we do in other
services, but I’m not in a hurry to do that as I believe
there was a masters project at ETH to replace chips with
something better… perhaps someone can fill us in on the
status of this, and if there are any merge plans?<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Andrew<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif""
lang="EN-US"> Zeus Gómez Marmolejo
[<a class="moz-txt-link-freetext" href="mailto:zeus.gomez@bsc.es">mailto:zeus.gomez@bsc.es</a>]
<br>
<b>Sent:</b> Thursday, 16 February, 2012 4:50<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:barrelfish-users@lists.inf.ethz.ch">barrelfish-users@lists.inf.ethz.ch</a><br>
<b>Subject:</b> [Barrelfish-users] System V Shared memory<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi all,<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I have been trying the shmget() shmat()
functions present in the posixcompat library, which are not
used by any program in Barrelfish. I've made two very simple
programs shm_client and shm_server which export a shared
memory and waits for the other to write on it. I attach the
two programs.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The system seems to work even on
different cores, but in this case I always get an error on
chips forcing it to abort:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal">ERROR: chips.0 in
get_service_reference_handler()
/home/zeus/bsc/bf/usr/chips/framework.c:167<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">get_service_reference_response failed<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Failure: ( flounder) Cannot queue
message for transmit: queue is full [FLOUNDER_ERR_TX_BUSY]<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">(I removed the original assert to see
the error).<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I guess the waitset has to be serviced
to process the ACKs and empty the queue. But, this
function is being called on the event handler.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Do you think is there an easy fix to
this problem?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Thanks,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">-- <br>
Zeus Gómez Marmolejo<br>
Barcelona Supercomputing Center<br>
PhD student<br>
<a moz-do-not-send="true" href="http://www.bsc.es"
target="_blank">http://www.bsc.es</a><br>
<br>
<o:p></o:p></p>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Barrelfish-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Barrelfish-users@lists.inf.ethz.ch">Barrelfish-users@lists.inf.ethz.ch</a>
<a class="moz-txt-link-freetext" href="https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users">https://lists.inf.ethz.ch/mailman/listinfo/barrelfish-users</a>
</pre>
</blockquote>
<br>
</body>
</html>