From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH 2/6] pcap: Update pcap_frame() to take an iovec and offset
Date: Tue, 27 Feb 2024 15:23:58 +0100 [thread overview]
Message-ID: <20240227152358.4550cbfa@elisabeth> (raw)
In-Reply-To: <20240222055602.1872516-3-david@gibson.dropbear.id.au>
On Thu, 22 Feb 2024 16:55:58 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> Update the low-level helper pcap_frame() to take a struct iovec and
> offset within it, rather than an explicit pointer and length for the
> frame. This moves the handling of an offset (to skip vnet_len) from
> pcap_multiple() to pcap_frame().
>
> This doesn't accomplish a great deal immediately, but will make
> subsequent changes easier.
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> pcap.c | 29 ++++++++++++-----------------
> 1 file changed, 12 insertions(+), 17 deletions(-)
>
> diff --git a/pcap.c b/pcap.c
> index 501d52d4..8876a051 100644
> --- a/pcap.c
> +++ b/pcap.c
> @@ -67,24 +67,25 @@ struct pcap_pkthdr {
>
> /**
> * pcap_frame() - Capture a single frame to pcap file with given timestamp
> - * @pkt: Pointer to data buffer, including L2 headers
> - * @len: L2 packet length
> + * @iov: iovec referencing buffer containing frame (with L2 headers)
For consistency with, say, 1/6: "IO vector"
--
Stefano
next prev parent reply other threads:[~2024-02-27 14:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 5:55 [PATCH 0/6] Allow more use of iovecs in pcap and tap interfaces David Gibson
2024-02-22 5:55 ` [PATCH 1/6] util: Add helper to find offset into io vector David Gibson
2024-02-27 14:23 ` Stefano Brivio
2024-02-27 23:27 ` David Gibson
2024-02-22 5:55 ` [PATCH 2/6] pcap: Update pcap_frame() to take an iovec and offset David Gibson
2024-02-27 14:23 ` Stefano Brivio [this message]
2024-02-22 5:55 ` [PATCH 3/6] util: Add write_remainder() helper David Gibson
2024-02-27 14:25 ` Stefano Brivio
2024-02-28 0:44 ` David Gibson
2024-02-28 6:24 ` Stefano Brivio
2024-02-28 9:04 ` David Gibson
2024-02-28 9:22 ` Stefano Brivio
2024-02-22 5:56 ` [PATCH 4/6] pcap: Handle short writes in pcap_frame() David Gibson
2024-02-22 5:56 ` [PATCH 5/6] pcap: Allow pcap_frame() and pcap_multiple() to take multi-buffer frames David Gibson
2024-02-27 14:26 ` Stefano Brivio
2024-02-22 5:56 ` [PATCH 6/6] tap: Use write_remainder() in tap_send_frames_passt() David Gibson
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=20240227152358.4550cbfa@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).