lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 15 May 2016 13:16:06 -0400 (EDT) From: David Miller <davem@...emloft.net> To: decui@...rosoft.com Cc: gregkh@...uxfoundation.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, devel@...uxdriverproject.org, olaf@...fle.de, apw@...onical.com, jasowang@...hat.com, cavery@...hat.com, kys@...rosoft.com, haiyangz@...rosoft.com, joe@...ches.com, vkuznets@...hat.com Subject: Re: [PATCH v11 net-next 0/1] introduce Hyper-V VM Sockets(hv_sock) From: Dexuan Cui <decui@...rosoft.com> Date: Sun, 15 May 2016 09:52:42 -0700 > Changes since v10 > > 1) add module params: send_ring_page, recv_ring_page. They can be used to > enlarge the ringbuffer size to get better performance, e.g., > # modprobe hv_sock recv_ring_page=16 send_ring_page=16 > By default, recv_ring_page is 3 and send_ring_page is 2. > > 2) add module param max_socket_number (the default is 1024). > A user can enlarge the number to create more than 1024 hv_sock sockets. > By default, 1024 sockets take about 1024 * (3+2+1+1) * 4KB = 28M bytes. > (Here 1+1 means 1 page for send/recv buffers per connection, respectively.) This is papering around my objections, and create module parameters which I am fundamentally against. You're making the facility unusable by default, just to work around my memory consumption concerns. What will end up happening is that everyone will simply increase the values. You're not really addressing the core issue, and I will be ignoring you future submissions of this change until you do.
Powered by blists - more mailing lists