Date: Wed, 27 Jul 2022 11:37:16 +0800 From: Chih-Hsin Chang <starbops@hey.com> To: freebsd-net@freebsd.org Subject: Question on Current Status of TCPUTO Socket Option Message-ID: <f4c3d360a7871fa01baa310075b606f83c3b842d@hey.com>
next in thread | raw e-mail | index | archive | help
----==_mimepart_62e0b2ecc5d82_6126fc198f4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hello, I'm working on OpenStack porting stuff recently. I encountered an issue that caused `nova-scheduler` unable to start normally. The `nova- scheduler` needs to build up connections to RabbitMQ with the aid of the RabbitMQ driver in the `oslo.messaging` library. The point is that the driver needs to configure a socket option called `TCP_USER_TIMEOUT` (defined in RFC5482) along the process but the socket option seems not to exist on the FreeBSD platform AFAIK. After searching on the web, I found there're two wiki pages and some patches working on FreeBSD `TCP_USER_TIMEOUT` implementation. But none of them were accepted or merged in the source tree. I would like to know about the current situation of the implementation of this socket option. Thank you. - https://github.com/openstack/oslo.messaging/blob/12.14.0/oslo_messaging/_drivers/impl_rabbit.py#L1025 - https://wiki.freebsd.org/FangWang/TCPUTO - https://wiki.freebsd.org/CatalinNicutar/TCPUTO Sincerely, Chih-Hsin Chang ----==_mimepart_62e0b2ecc5d82_6126fc198f4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html> <html> <head> <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf= -8" /> <meta name=3D"viewport" id=3D"viewport" content=3D"width=3Ddevice-wid= th,minimum-scale=3D1.0,maximum-scale=3D10.0,initial-scale=3D1.0" /> <style> html{-webkit-text-size-adjust:100%;-ms-text-size-adjust:100%}h1{fon= t-size:1.3em;line-height:1.2;margin:0}ul,ol{margin:0;padding:0}ul li,ol l= i,li li{margin:0 0 0 36px}[dir=3Drtl] li{margin:0 18px 0 0}blockquote{bor= der-color:#dfdee1;border-style:solid;border-width:0 0 0 1px;margin:0;padd= ing:0 0 0 1em}[dir=3Drtl] blockquote,blockquote[dir=3Drtl]{border-width:0= 1px 0 0;padding:0 1em 0 0}pre{font-family:"SFMono-Regular",Consolas,"Lib= eration Mono",Menlo,Courier,monospace;font-size:.9em;margin:0;padding:1re= m;background-color:#f6f5f3;white-space:pre-wrap;word-wrap:break-word;over= flow:visible}.message-content{font-family:-apple-system,BlinkMacSystemFon= t,"Segoe UI",Roboto,Helvetica,Arial,sans-serif,"Apple Color Emoji","Segoe= UI Emoji","Segoe UI Symbol";line-height:1.4}.attachment{display:inline-b= lock;margin:0;padding:0}.attachment__caption{padding:0;text-align:center}= .attachment__caption a[href]{text-decoration:none;color:#333}.attachment-= -preview{width:100%;text-align:center;margin:.625em 0}.attachment--previe= w img{border:1px solid #dfdee1;vertical-align:middle;width:auto;max-width= :100%;max-height:640px}.attachment--preview .attachment__caption{color:#7= 16d7b;font-size:.85em;margin-top:.625em}.attachment--file{color:#282138;l= ine-height:1;margin:0 2px 2px 0;padding:.4em 1em;border:1px solid #dfdee1= ;border-radius:5px}.permalink{color:inherit}.txt--xx-small{font-size:14px= }.flush{margin:0;padding:0}.push--bottom{margin-bottom:8px}.border--top{b= order-top:1px solid #ece9e6}.btn{padding:.2em .4em;font-weight:500;text-d= ecoration:none;border-radius:3rem;white-space:nowrap;background:#5522fa;b= order-color:#5522fa;color:#fff}.btn--email{display:inline-block;text-alig= n:center;font-weight:500;font-size:1em;text-decoration:none;border-radius= :2em;white-space:nowrap;background:#5522fa;border-color:#5522fa;color:#ff= f;border-top:.3em solid #5522fa;border-left:1em solid #5522fa;border-bott= om:.3em solid #5522fa;border-right:1em solid #5522fa}.shaded{padding:1em;= border-radius:4px;background-color:#f6f5f3;border:1px solid #dfdee1} </style> </head> <body> <div class=3D"message-content"> <div class=3D"trix-content"> <div>Hello,<br><br>I'm working on OpenStack porting stuff recently. I e= ncountered an issue that caused `nova-scheduler` unable to start normally= . The `nova-scheduler` needs to build up connections to RabbitMQ with the= aid of the RabbitMQ driver in the `oslo.messaging` library. The point is= that the driver needs to configure a socket option called `TCP_USER_TIME= OUT` (defined in RFC5482) along the process but the socket option seems n= ot to exist on the FreeBSD platform AFAIK.<br><br>After searching on the = web, I found there're two wiki pages and some patches working on FreeBSD = `TCP_USER_TIMEOUT` implementation. But none of them were accepted or merg= ed in the source tree. I would like to know about the current situation o= f the implementation of this socket option.<br><br>Thank you.<br><br>- ht= tps://github.com/openstack/oslo.messaging/blob/12.14.0/oslo_messaging/_dr= ivers/impl_rabbit.py#L1025<br>- https://wiki.freebsd.org/FangWang/TCPUTO<= br>- https://wiki.freebsd.org/CatalinNicutar/TCPUTO<br><br>Sincerely,<br>= Chih-Hsin Chang</div> </div> </div> </body> </html> ----==_mimepart_62e0b2ecc5d82_6126fc198f4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f4c3d360a7871fa01baa310075b606f83c3b842d>