[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190522.180047.238715219030499893.davem@davemloft.net>
Date: Wed, 22 May 2019 18:00:47 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: sunilmut@...rosoft.com
Cc: kys@...rosoft.com, haiyangz@...rosoft.com, sthemmin@...rosoft.com,
sashal@...nel.org, decui@...rosoft.com, mikelley@...rosoft.com,
netdev@...r.kernel.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] hv_sock: perf: Allow the socket buffer size
options to influence the actual socket buffers
From: Sunil Muthuswamy <sunilmut@...rosoft.com>
Date: Wed, 22 May 2019 22:56:07 +0000
> Currently, the hv_sock buffer size is static and can't scale to the
> bandwidth requirements of the application. This change allows the
> applications to influence the socket buffer sizes using the SO_SNDBUF and
> the SO_RCVBUF socket options.
>
> Few interesting points to note:
> 1. Since the VMBUS does not allow a resize operation of the ring size, the
> socket buffer size option should be set prior to establishing the
> connection for it to take effect.
> 2. Setting the socket option comes with the cost of that much memory being
> reserved/allocated by the kernel, for the lifetime of the connection.
>
> Perf data:
> Total Data Transfer: 1GB
> Single threaded reader/writer
> Results below are summarized over 10 iterations.
...
> Signed-off-by: Sunil Muthuswamy <sunilmut@...rosoft.com>
Applied.
Powered by blists - more mailing lists