From: Konstantin Shkolnyy <kshk@linux.ibm.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: virtualization@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, mjrosato@linux.ibm.com
Subject: Re: [PATCH v6 3/3] vsock/test: verify socket options after setting them
Date: Mon, 18 Nov 2024 09:54:04 -0600 [thread overview]
Message-ID: <542cb6ed-8e2b-407e-9f9d-037144740b93@linux.ibm.com> (raw)
In-Reply-To: <yo2qj7psn3sqtyqgsfn6y2qtwcmyb4j7gwuffg34gwqwkrsyox@4aff3wvdrdgu>
On 11/14/2024 04:28, Stefano Garzarella wrote:
> On Wed, Nov 13, 2024 at 08:35:57AM -0600, Konstantin Shkolnyy wrote:
[...]
>> diff --git a/tools/testing/vsock/msg_zerocopy_common.c b/tools/
>> testing/vsock/msg_zerocopy_common.c
>> index 5a4bdf7b5132..8622e5a0f8b7 100644
>> --- a/tools/testing/vsock/msg_zerocopy_common.c
>> +++ b/tools/testing/vsock/msg_zerocopy_common.c
>> @@ -14,16 +14,6 @@
>>
>> #include "msg_zerocopy_common.h"
>>
>> -void enable_so_zerocopy(int fd)
>> -{
>> - int val = 1;
>> -
>> - if (setsockopt(fd, SOL_SOCKET, SO_ZEROCOPY, &val, sizeof(val))) {
>> - perror("setsockopt");
>> - exit(EXIT_FAILURE);
>> - }
>> -}
>> -
>
> Since the new API has a different name (i.e.
> `enable_so_zerocopy_check()`), this `enable_so_zerocopy()` could stay
> here, anyway I don't want to be too picky, I'm totally fine with this
> change since it's now only used by vsock_perf ;-)
>
> Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
>
Ok, let's keep it static then - it's simpler :-)
next prev parent reply other threads:[~2024-11-18 15:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 14:35 [PATCH v6 0/3] vsock/test: fix wrong setsockopt() parameters Konstantin Shkolnyy
2024-11-13 14:35 ` [PATCH v6 1/3] vsock/test: fix failures due to wrong SO_RCVLOWAT parameter Konstantin Shkolnyy
2024-11-13 14:35 ` [PATCH v6 2/3] vsock/test: fix parameter types in SO_VM_SOCKETS_* calls Konstantin Shkolnyy
2024-11-13 14:35 ` [PATCH v6 3/3] vsock/test: verify socket options after setting them Konstantin Shkolnyy
2024-11-14 10:28 ` Stefano Garzarella
2024-11-18 15:54 ` Konstantin Shkolnyy [this message]
2024-12-02 15:54 ` [PATCH v6 0/3] vsock/test: fix wrong setsockopt() parameters Stefano Garzarella
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=542cb6ed-8e2b-407e-9f9d-037144740b93@linux.ibm.com \
--to=kshk@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).