[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20191014083836.fumqbp4sfn5usys6@steredhat>
Date: Mon, 14 Oct 2019 10:38:36 +0200
From: Stefano Garzarella <sgarzare@...hat.com>
To: Jason Wang <jasowang@...hat.com>,
Stefan Hajnoczi <stefanha@...hat.com>
Cc: Stefan Hajnoczi <stefanha@...hat.com>,
"Michael S. Tsirkin" <mst@...hat.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
"David S. Miller" <davem@...emloft.net>,
virtualization@...ts.linux-foundation.org,
kvm <kvm@...r.kernel.org>
Subject: Re: [PATCH v4 1/5] vsock/virtio: limit the memory used per-socket
On Mon, Oct 14, 2019 at 04:21:35PM +0800, Jason Wang wrote:
> On 2019/10/14 下午4:17, Stefan Hajnoczi wrote:
> > SO_VM_SOCKETS_BUFFER_SIZE might have been useful for VMCI-specific
> > applications, but we should use SO_RCVBUF and SO_SNDBUF for portable
> > applications in the future. Those socket options also work with other
> > address families.
> >
I think hyperv_transport started to use it in this patch:
ac383f58f3c9 hv_sock: perf: Allow the socket buffer size options to influence
the actual socket buffers
> > I guess these sockopts are bypassed by AF_VSOCK because it doesn't use
> > the common skb queuing code in net/core/sock.c:(. But one day we might
> > migrate to it...
> >
> > Stefan
>
>
> +1, we should really consider to reuse the exist socket mechanism instead of
> re-inventing wheels.
+1, I totally agree. I'll go this way.
Guys, thank you all for your suggestions!
Powered by blists - more mailing lists