public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Maloy <jmaloy@redhat.com>
Cc: Stefano Brivio <sbrivio@redhat.com>,
	lvivier@redhat.com, dgibson@redhat.com, passt-dev@passt.top
Subject: Re: [RFC v2] tcp: add support for read with offset when using MSG_PEEK
Date: Tue, 5 Sep 2023 12:16:11 +1000	[thread overview]
Message-ID: <ZPaPa3HnCNZTl4Ib@zatzit> (raw)
In-Reply-To: <e7e5c9b2-1b13-2c33-3261-cbda8076262d@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2224 bytes --]

On Mon, Sep 04, 2023 at 01:14:17PM -0400, Jon Maloy wrote:
> 
> 
> On 2023-06-23 07:02, Stefano Brivio wrote:
> > On Thu, 22 Jun 2023 22:12:27 -0400
> > Jon Maloy <jmaloy@redhat.com> wrote:
> > 
> > > When reading received messages with MSG_PEEK, we sometines have to read
> > > the leading bytes of the stream several times, only to reach the bytes
> > > we really want. This is clearly non-optimal.
> > > 
> > > What we would want is something similar to pread/preadv(), but working
> > > even for tcp sockets. At the same time, we obviously don't want to add
> > > any new arguments to the recv/recvmsg() calls.
> > > 
> > > In this commit, we allow the user to set iovec.iov_base in the first
> > > vector entry to NULL. This tells the socket to skip the first entry,
> > > hence making the iov_len field of that entry indicate the offset value.
> > > This way, there is no need to add any new arguments.
> > Ah-ha! I'm glad you found an acceptable way to pass a NULL pointer
> > there. :)
> > 
> > > This change is simple and non-intrusive, and should be safe addition to
> > > the socket API. We have measured it to give a throughput improvement of
> > ...it would be nice to also do a bit of profiling with perf(1) --
> > that's where I originally noticed we were wasting cycles on filling up
> > tcp_buf_discard. Plus, sure, there's also some value in dropping a
> > useless 16 MiB buffer.
> > 
> > If you need examples/inspiration: the pasta (automated) demo shows
> > that, skip at 9:20 in: https://passt.top/passt/about/#pasta_2 (the one
> > on the left)
> > 
> > and that's simply done like this:
> >    https://passt.top/passt/tree/test/demo/pasta#n163
> This looks like a script language, but I don't recognize it. How do I run
> it?

It's the hand rolled script language of the passt tests.  The
interpreter is in test/lib/test.  Easiest way to run it is probably to
"make check" in test/ of the passt tree.  If you want to selectively
run certain things, edit test/run.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-09-05  2:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  2:12 [RFC v2] tcp: add support for read with offset when using MSG_PEEK Jon Maloy
2023-06-23  2:36 ` Jon Maloy
2023-06-23 11:02 ` Stefano Brivio
2023-09-04 17:14   ` Jon Maloy
2023-09-05  2:16     ` David Gibson [this message]
2023-09-05  6:19       ` Stefano Brivio

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=ZPaPa3HnCNZTl4Ib@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=dgibson@redhat.com \
    --cc=jmaloy@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.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.
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).