From: John Fastabend <john.fastabend@gmail.com>
To: Martin KaFai Lau <kafai@fb.com>
Cc: borkmann@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org
Subject: Re: [bpf-next PATCH v2 3/7] bpf: sockmap sample, use fork() for send and recv
Date: Thu, 11 Jan 2018 19:57:18 -0800 [thread overview]
Message-ID: <79e7710f-4f24-4199-bc0e-eea9a55adee6@gmail.com> (raw)
In-Reply-To: <20180111210853.7jnrkogn54hhavjj@kafai-mbp.dhcp.thefacebook.com>
On 01/11/2018 01:08 PM, Martin KaFai Lau wrote:
> On Wed, Jan 10, 2018 at 10:39:37AM -0800, John Fastabend wrote:
>> Currently for SENDMSG tests first send completes then recv runs. This
>> does not work well for large data sizes and/or many iterations. So
>> fork the recv and send handler so that we run both send and recv. In
>> the future we can add a parameter to do more than a single fork of
>> tx/rx.
>>
>> With this we can get many GBps of data which helps exercise the
>> sockmap code.
>>
>> Signed-off-by: John Fastabend <john.fastabend@gmail.com>
>> ---
[...]
>> static int sendmsg_test(int iov_count, int iov_buf, int cnt, int verbose)
>> {
>> + int txpid, rxpid, err = 0;
>> struct msg_stats s = {0};
>> - int err;
>> -
>> - err = msg_loop(c1, iov_count, iov_buf, cnt, &s, true);
>> - if (err) {
>> - fprintf(stderr,
>> - "msg_loop_tx: iov_count %i iov_buf %i cnt %i err %i\n",
>> - iov_count, iov_buf, cnt, err);
>> - return err;
>> + int status;
>> +
>> + errno = 0;
>> +
>> + rxpid = fork();
>> + if (rxpid == 0) {
>> + err = msg_loop(p2, iov_count, iov_buf, cnt, &s, false);
>> + if (err)
>> + fprintf(stderr,
>> + "msg_loop_rx: iov_count %i iov_buf %i cnt %i err %i\n",
>> + iov_count, iov_buf, cnt, err);
>> + fprintf(stdout, "rx_sendmsg: TX_bytes %zu RX_bytes %zu\n",
>> + s.bytes_sent, s.bytes_recvd);
>> + shutdown(p2, SHUT_RDWR);
>> + shutdown(p1, SHUT_RDWR);
>> + exit(1);
>> + } else if (rxpid == -1) {
>> + perror("msg_loop_rx: ");
>> + err = errno;
> Bail out here instead of continuing the tx side?
>
Sure makes sense. No point in running the TX side here I guess.
next prev parent reply other threads:[~2018-01-12 3:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 18:38 [bpf-next PATCH v2 0/7] sockmap sample update John Fastabend
2018-01-10 18:39 ` [bpf-next PATCH v2 1/7] bpf: refactor sockmap sample program update for arg parsing John Fastabend
2018-01-11 1:25 ` Daniel Borkmann
2018-01-12 4:31 ` John Fastabend
2018-01-12 4:58 ` John Fastabend
2018-01-11 21:05 ` Martin KaFai Lau
2018-01-12 3:54 ` John Fastabend
2018-01-10 18:39 ` [bpf-next PATCH v2 2/7] bpf: add sendmsg option for testing BPF programs John Fastabend
2018-01-11 1:28 ` Daniel Borkmann
2018-01-11 21:08 ` Martin KaFai Lau
2018-01-10 18:39 ` [bpf-next PATCH v2 3/7] bpf: sockmap sample, use fork() for send and recv John Fastabend
2018-01-11 1:31 ` Daniel Borkmann
2018-01-12 4:33 ` John Fastabend
2018-01-11 21:08 ` Martin KaFai Lau
2018-01-12 3:57 ` John Fastabend [this message]
2018-01-10 18:39 ` [bpf-next PATCH v2 4/7] bpf: sockmap sample, report bytes/sec John Fastabend
2018-01-10 18:40 ` [bpf-next PATCH v2 5/7] bpf: sockmap sample add base test without any BPF for comparison John Fastabend
2018-01-11 21:10 ` Martin KaFai Lau
2018-01-12 4:03 ` John Fastabend
2018-01-10 18:40 ` [bpf-next PATCH v2 6/7] bpf: sockmap put client sockets in blocking mode John Fastabend
2018-01-10 18:40 ` [bpf-next PATCH v2 7/7] bpf: sockmap set rlimit John Fastabend
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=79e7710f-4f24-4199-bc0e-eea9a55adee6@gmail.com \
--to=john.fastabend@gmail.com \
--cc=ast@kernel.org \
--cc=borkmann@iogearbox.net \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
/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).