[vpp-dev] vppcom_session_connect blocking or non blocking

Hello, Can vppcom_session_connect() function run in non-blocking mode? I see that there is a wait for the connection result in the vppcom_wait_for_session_state_change function. Is it possible to get the result of the connection using vppcom_epoll_wait? Thanks. -=-=-=-=-=-=-=-=-=-=-=- Links:

[vpp-dev] VLC: tls in open tcp session

Hello, Is it possible to switch to using TLS in an already open TCP session using VCL? Thanks. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13987): https://lists.fd.io/g/vpp-dev/message/13987 Mute This Topic:

Re: [vpp-dev] vppcom_session_connect blocking or non blocking

15, 2019, at 7:41 AM, Florin Coras via Lists.Fd.Io < >>fcoras.lists=gmail@lists.fd.io > wrote: >>Hi Max, >> >>Not at this time. It should be possible with a few changes for nonblocking >>sessions. I’ll add it to my list, in case nobody else beats me to

Re: [vpp-dev] TCP host stack & small size fifo

Hi Florin, I simplified the application. It sends the request and reads all the data from the server using the 8 KB buffer. The fifo size is set to 8 KB. In the attached dump [1] you can see that in packet number 14 there will be an overflow of the size of the tcp window. My application

Re: [vpp-dev] TCP host stack & small size fifo

Hi Florin, I made a simple epoll tcp proxy (using vcl) and saw the same behavior. I increased the fifo size to 16k, but I got exactly the same effect.  A full dump for a session with a buffer size of 16k can be obtained by reference [1] (192.168.0.1 is the interface on vpp, 192.168.0.200 is

Re: [vpp-dev] TCP host stack & small size fifo

Hi Florin, > >Well, the question there is how large are the rx buffers. If you never see a >zero rcv window advertised to the sender, I suspect the rx buffer is large >enough to sustain the throughput.  Using the reference [1], you can view a dump of downloading the same file from the same

Re: [vpp-dev] TCP host stack & small size fifo

Hi Florin, >As explained above, as long as the sender is faster, this will happen. Still, >out of curiosity, can you try this [1] to see if it changes linux’s behavior >in any way? Although, I suspect the linux’s window probe timer, after a zero >window, is not smaller than min rto (which is

Re: [vpp-dev] TCP host stack & small size fifo

Hi Florin, I tried to increase the buffer size to 128k. The problem still arises, only less often [1]. The smaller the buffer, the more often the problem occurs. Thanks. [1] https://drive.google.com/open?id=1KVSzHhPscpSNkdLN0k2gddPJwccpguoo   -- Max A. -=-=-=-=-=-=-=-=-=-=-=- Links: You

Re: [vpp-dev] TCP host stack & small size fifo

Hi Florin, > >That’s an important difference because in case of the proxy, you cannot >dequeue the data from the fifo before you send it to the actual destination >and it gets acknowledged. That means, you need to wait at least one rtt (to >the final destination) before you can make space in

Re: [vpp-dev] vppcom_session_connect blocking or non blocking

t;Hi Max, >> >>Not at this time. It should be possible with a few changes for nonblocking >>sessions. I’ll add it to my list, in case nobody else beats me to it. >> >>Florin >>  >>>On Aug 15, 2019, at 2:47 AM, Max A. via Lists.Fd.Io < >>

Re: [vpp-dev] vppcom_session_connect blocking or non blocking

p/+/21610 >>>  >>>>On Aug 15, 2019, at 7:41 AM, Florin Coras via Lists.Fd.Io < >>>>fcoras.lists=gmail@lists.fd.io > wrote:   >>>>Hi Max, >>>> >>>>Not at this time. It should be possible with a few changes for nonblocking