From: Kui-Feng Lee <sinquersw@gmail.com>
To: Stanislav Fomichev <sdf@fomichev.me>
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
Kui-Feng Lee <thinker.li@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, song@kernel.org,
kernel-team@meta.com, andrii@kernel.org, kuifeng@meta.com
Subject: Re: [PATCH bpf-next 0/4] monitor network traffic for flaky test cases
Date: Mon, 15 Jul 2024 23:46:17 -0700 [thread overview]
Message-ID: <ce96aa60-bb14-498f-b996-ab906a3b9f0d@gmail.com> (raw)
In-Reply-To: <ZpXoODGNDyhnyeO8@mini-arch>
On 7/15/24 20:25, Stanislav Fomichev wrote:
> On 07/15, Kui-Feng Lee wrote:
>>
>>
>> On 7/15/24 16:56, Martin KaFai Lau wrote:
>>> On 7/15/24 3:07 PM, Kui-Feng Lee wrote:
>>>>
>>>>
>>>> On 7/15/24 14:33, Stanislav Fomichev wrote:
>>>>> On 07/12, Kui-Feng Lee wrote:
>>>>>> Run tcpdump in the background for flaky test cases related to network
>>>>>> features.
>>>>>
>>>>> Have you considered linking against libpcap instead of shelling out
>>>>> to tcpdump? As long as we have this lib installed on the runners
>>>>> (likely?) that should be a bit cleaner than doing tcpdump.. WDYT?
>>>>
>>>> I just checked the script building the root image for vmtest. [1]
>>>> It doesn't install libpcap.
>>>>
>>>> If our approach is to capture the packets in a file, and let developers
>>>> download the file, it would be a simple and straight forward solution.
>>>> If we want a log in text, it would be more complicated to parse
>>>> packets.
>>>>
>>>> Martin & Stanislay,
>>>>
>>>> WDYT about capture packets in a file and using libpcap directly?
>>>> Developers can download the file and parse it with tcpdump locally.
>>>
>>> thinking out loud...
>>>
>>> Re: libpcap (instead of tcpdump) part. I am not very experienced in
>>> libpcap. I don't have a strong preference. I do hope patch 1 could be
>>> more straight forward that no need to use loops and artificial udp
>>> packets to ensure the tcpdump is fully ready to capture. I assume using
>>> libpcap can make this sync part easier/cleaner (pthread_cond?) and not
>>> too much code is needed to use libpcap?
>>
>> Yes, it would be easier and cleaner if we don't parse the payload
>> of packets.
>
> Yeah, same, no strong preference; was just wondering whether you've
> made a conscious choice of not using it because it definitely makes things
> a bit easier wrt to the part where you try to sync with tcpdump..
>
> Also +1 on saving the raw file (via libpcap or tcpdump -w).
I agree to do it with libpcap. And, will print a number to stdout/stderr
as an index to the packets in the raw file. However, I need to figure
out how to make the raw file available to developers at first.
prev parent reply other threads:[~2024-07-16 6:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-13 5:55 [PATCH bpf-next 0/4] monitor network traffic for flaky test cases Kui-Feng Lee
2024-07-13 5:55 ` [PATCH bpf-next 1/4] selftests/bpf: Add traffic monitor functions Kui-Feng Lee
2024-07-14 0:18 ` Kui-Feng Lee
2024-07-14 15:27 ` kernel test robot
2024-07-13 5:55 ` [PATCH bpf-next 2/4] selftests/bpf: Monitor traffic for tc_redirect/tc_redirect_dtime Kui-Feng Lee
2024-07-13 5:55 ` [PATCH bpf-next 3/4] selftests/bpf: Monitor traffic for sockmap_listen Kui-Feng Lee
2024-07-13 5:55 ` [PATCH bpf-next 4/4] selftests/bpf: Monitor traffic for select_reuseport Kui-Feng Lee
2024-07-13 19:29 ` [PATCH bpf-next 0/4] monitor network traffic for flaky test cases Kui-Feng Lee
2024-07-15 21:33 ` Stanislav Fomichev
2024-07-15 22:07 ` Kui-Feng Lee
2024-07-15 23:56 ` Martin KaFai Lau
2024-07-16 0:57 ` Kui-Feng Lee
2024-07-16 3:25 ` Stanislav Fomichev
2024-07-16 6:46 ` Kui-Feng Lee [this message]
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=ce96aa60-bb14-498f-b996-ab906a3b9f0d@gmail.com \
--to=sinquersw@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=kernel-team@meta.com \
--cc=kuifeng@meta.com \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=thinker.li@gmail.com \
/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