<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Socket Buffer Handling in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/socket-buffer-handling/m-p/3703607#M73562</link>
    <description>&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;... and they said that "it is common knowledge"&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;Trouble is, by that definition there are not many common people!&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
    <pubDate>Fri, 06 Jan 2006 12:21:32 GMT</pubDate>
    <dc:creator>Jan van den Ende</dc:creator>
    <dc:date>2006-01-06T12:21:32Z</dc:date>
    <item>
      <title>Socket Buffer Handling</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/socket-buffer-handling/m-p/3703604#M73559</link>
      <description>Hi ,&lt;BR /&gt;&lt;BR /&gt;Could any one provide me detail information about the following -&lt;BR /&gt;&lt;BR /&gt;UCX&amp;gt; show dev bg1396/fu&lt;BR /&gt;Device_socket: bg1396 Type: STREAM LOCAL REMOTE&lt;BR /&gt;Port: 23 1216&lt;BR /&gt;Host: TGDV12 THDV42&lt;BR /&gt;Service: TELNET Terminal: TNA1:&lt;BR /&gt;&lt;BR /&gt;RECEIVE SEND&lt;BR /&gt;Queued I/O 0 0&lt;BR /&gt;Q0LEN 0 Socket buffer bytes 0 2&lt;BR /&gt;QLEN 0 Socket buffer quota 3000 3000&lt;BR /&gt;QLIMIT 0 Total buffer alloc 0 1828&lt;BR /&gt;TIMEO 0 Total buffer limit 12000 12000&lt;BR /&gt;ERROR 0 Number of XONs 0 0&lt;BR /&gt;OOBMARK 0 Number of XOFFs 0 0&lt;BR /&gt;I/O completed 243 386&lt;BR /&gt;Bytes transferred 390 13575&lt;BR /&gt;&lt;BR /&gt;Options: REUSEADR KEEP OOBINLINE&lt;BR /&gt;State: ISCONNECTED PRIV&lt;BR /&gt;RCV Buff: WAIT&lt;BR /&gt;SND Buff: SEL&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;What is the meaning of the bottom section -&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Options: REUSEADR KEEP OOBINLINE&lt;BR /&gt;State: ISCONNECTED PRIV&lt;BR /&gt;RCV Buff: WAIT&lt;BR /&gt;SND Buff: SEL&lt;BR /&gt;i.e. -&amp;gt; Option: keep or Option: REUSEADR or RCV Buff: WAIT etc ..&lt;BR /&gt;&lt;BR /&gt;Could any one provide me any document/manual explaing this all for UCX 4.2. I am trying to tune the parameters for better buffer handing as per my system requirements.&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Thu, 05 Jan 2006 11:21:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/socket-buffer-handling/m-p/3703604#M73559</guid>
      <dc:creator>Mainak</dc:creator>
      <dc:date>2006-01-05T11:21:44Z</dc:date>
    </item>
    <item>
      <title>Re: Socket Buffer Handling</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/socket-buffer-handling/m-p/3703605#M73560</link>
      <description>REUSEADR KEEP OOBINLINE&lt;BR /&gt;&lt;BR /&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;You will find the description of the socket options in &lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/82final/6529/6529pro_028.html#app_sock_options" target="_blank"&gt;http://h71000.www7.hp.com/doc/82final/6529/6529pro_028.html#app_sock_options&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;For instance :&lt;BR /&gt;SO_REUSEADDR &lt;BR /&gt; Specifies that the rules used in validating addresses supplied by a bind() function should allow reuse of local addresses. A value of 0 disables the option, and a non-zero value enables the option. The SO_REUSEPORT option is automatically set when an application sets SO_REUSEADDR.  &lt;BR /&gt;&lt;BR /&gt;...</description>
      <pubDate>Fri, 06 Jan 2006 11:40:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/socket-buffer-handling/m-p/3703605#M73560</guid>
      <dc:creator>faris_3</dc:creator>
      <dc:date>2006-01-06T11:40:09Z</dc:date>
    </item>
    <item>
      <title>Re: Socket Buffer Handling</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/socket-buffer-handling/m-p/3703606#M73561</link>
      <description>I once asked HP if they had a description of all those fields and they said that "it is common knowledge" t.i. undocumented unless you read the sources.&lt;BR /&gt;&lt;BR /&gt;So, find the sources of a tcp version. Often there is some comment in it. Don't like it myself but it is trendy (open stuff).&lt;BR /&gt;&lt;BR /&gt;Wim</description>
      <pubDate>Fri, 06 Jan 2006 11:55:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/socket-buffer-handling/m-p/3703606#M73561</guid>
      <dc:creator>Wim Van den Wyngaert</dc:creator>
      <dc:date>2006-01-06T11:55:27Z</dc:date>
    </item>
    <item>
      <title>Re: Socket Buffer Handling</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/socket-buffer-handling/m-p/3703607#M73562</link>
      <description>&lt;BR /&gt;&lt;QUOTE&gt;&lt;BR /&gt;... and they said that "it is common knowledge"&lt;BR /&gt;&lt;/QUOTE&gt;&lt;BR /&gt;Trouble is, by that definition there are not many common people!&lt;BR /&gt;&lt;BR /&gt;Proost.&lt;BR /&gt;&lt;BR /&gt;Have one on me.&lt;BR /&gt;&lt;BR /&gt;jpe</description>
      <pubDate>Fri, 06 Jan 2006 12:21:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/socket-buffer-handling/m-p/3703607#M73562</guid>
      <dc:creator>Jan van den Ende</dc:creator>
      <dc:date>2006-01-06T12:21:32Z</dc:date>
    </item>
  </channel>
</rss>

