On Mon, Jul 29, 2019 at 3:51 PM Yi-Hung Wei <[email protected]> wrote:
> On Mon, Jul 29, 2019 at 1:12 PM Darrell Ball <[email protected]> wrote: > >> > "is_default" - can you explain this one ? > >> > >> This flag is used to configure the default timeout policy in the > >> datapath. If 'is_default' is true, it will set the provided timeout > >> policy to be the default timeout policy. The default timeout policy is > >> documented in vswitchd/vswitch.xml > >> > > > > Below is what I see the the schema xml file under timeout policy > > Please add description about the 'default' timeout policy under > > "CT_Timeout_Policy" - let me know if you need help, as I can submit a > patch. > > It is a few lines before what you pasted below. > > <table name="CT_Zone"> > Connection tracking zone configuration > > <column name="timeout_policy"> > Connection tracking timeout policy for this zone. If timeout policy is > not specified, defaults to the timeout policy in the default zone. If > the timeout policy in default zone is not specified, defaults to the > default timeouts in the system. > </column> > > <group title="Common Columns"> > The overall purpose of these columns is described under <code>Common > Columns</code> at the beginning of this document. > > <column name="external_ids"/> > </group> > </table> > Since we decided to remove the default zone timeout policy defaulting, I think this all becomes moot. > > > -Yi-Hung > > > > <table name="CT_Timeout_Policy"> > > Connection tracking timeout policy configuration > > > > <group title="Timeouts"> > > <column name="timeouts"> > > The <code>timeouts</code> column contains key-value pairs used > > to configure connection tracking timeouts in a datapath. > > Key-value pairs that are not supported by a datapath are > > ignored. > > </column> > > > > <group title="TCP Timeouts"> > > <column name="timeouts" key="tcp_syn_sent"> > > TCP SYN sent timeout. > > </column> > > > > <column name="timeouts" key="tcp_syn_recv"> > > TCP SYN receive timeout. > > </column> > > > > <column name="timeouts" key="tcp_established"> > > TCP established timeout. > > </column> > > > > <column name="timeouts" key="tcp_fin_wait"> > > TCP FIN wait timeout. > > </column> > > > > <column name="timeouts" key="tcp_close_wait"> > > TCP close wait timeout. > > </column> > > > > <column name="timeouts" key="tcp_last_ack"> > > TCP last ACK timeout. > > </column> > > > > <column name="timeouts" key="tcp_time_wait"> > > TCP time wait timeout. > > </column> > > > > <column name="timeouts" key="tcp_close"> > > TCP close timeout. > > </column> > > > > <column name="timeouts" key="tcp_syn_sent2"> > > TCP syn sent2 timeout. > > </column> > > > > <column name="timeouts" key="tcp_retransmit"> > > TCP retransmit timeout. > > </column> > > > > <column name="timeouts" key="tcp_unack"> > > TCP unacknowledgment timeout. > > </column> > > </group> > > > > <group title="UDP Timeouts"> > > <column name="timeouts" key="udp_first"> > > First UDP packet timeout. > > </column> > > > > <column name="timeouts" key="udp_single"> > > The timeout in the state that source host sends more than one > packet > > but the destination host has never sent one backs. > > </column> > > > > <column name="timeouts" key="udp_multiple"> > > UDP packets seen in both directions timeout. > > </column> > > </group> > > > > <group title="ICMP Timeouts"> > > <column name="timeouts" key="icmp_first"> > > First ICMP timeout. > > </column> > > > > <column name="timeouts" key="icmp_reply"> > > ICMP reply timeout. > > </column> > > </group> > > </group> > _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
