On 11/8/07, <b class="gmail_sendername">Olaf Kirch</b> <<a href="mailto:olaf.kirch@oracle.com">olaf.kirch@oracle.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Does anyone understand the meaning of the RDS_CONG_{SET,RELEASED}<br>poll flags? They seem utterly pointless to me.<br>...<br>So I think the RDS_CONG_* flags should go.<br>Comments?</blockquote><div><br>
Olaf, All<br>
<br>
I am not yet enough into the details to provide feedback on the patch, however thanks<br>
for sending it over this list, its a step forward.<br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">From: Olaf Kirch <<a href="mailto:olaf.kirch@oracle.com">olaf.kirch@oracle.com
</a>><br>RDS: nuke RDS_CONG_{SET,RELEASED}<br>
</blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Index: build-2.6-4/net/rds/af_rds.c<br></blockquote></div><br>
It will be very helpful for the develpment process if you set a git
tree with v2 and v3 branches such that patches you send or sent to you
would be against this tree / branch, how does this sound to you?<br>
<br>
I am leaving tomorrow for Oracle World and later SC07 and hence would
have less time to continue with my getting-into-rds, however, I will
try to be around and get on the call next Tuesday.<br>
<br>
Or.<br>