public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Eugenio Perez Martin <eperezma@redhat.com>
Cc: passt-dev@passt.top, Jason Wang <jasowang@redhat.com>,
	Jeff Nelson <jenelson@redhat.com>,
	Paul Holzinger <pholzing@redhat.com>
Subject: Re: vhost-kernel net on pasta: from 26 to 37Gbit/s
Date: Wed, 11 Jun 2025 10:08:16 +0200	[thread overview]
Message-ID: <20250611100816.71bbf48a@elisabeth> (raw)
In-Reply-To: <CAJaqyWcWMhSfrajNpVwpRMda3x5Y62QvrpWRRRXrVrR9gx78nQ@mail.gmail.com>

On Wed, 11 Jun 2025 09:04:57 +0200
Eugenio Perez Martin <eperezma@redhat.com> wrote:

> On Tue, Jun 10, 2025 at 5:29 PM Stefano Brivio <sbrivio@redhat.com> wrote:
> >
> > On Mon, 9 Jun 2025 11:59:21 +0200
> > Eugenio Perez Martin <eperezma@redhat.com> wrote:
> >  
> > > Getting a table like [1] would give us light about this, especially if
> > > it is just a matter of running "make performance" or similar. Maybe we
> > > need to include longer queues? Focus on a given scenario? UDP goes
> > > better but TCP?  
> >
> > Well, it's a matter of running ./run under tests (or 'make' there).
> > Have you tried that with your patch? It's kind of representative in the
> > sense that it uses several message sizes and different values for the
> > sending window.
> 
> Yes but it freezes in my env.
> 
> Copying the different windows, top-left:
> # tail -f --retry /home/passt/test/test_logs/context_unshare.log
> /home/passt/test/test_logs/context_ns.log
> tail: warning: --retry only effective for the initial open
> ==> /home/passt/test/test_logs/context_unshare.log <==  
> unshare$ tail: cannot open '/home/passt/test/test_logs/context_ns.log'
> for reading: No such file or directory
>
> [...]
>
> === build/cppcheck
> ...skipped.
> 
> 
> === build/clang_tidy
> ...skipped.
> ---

I guess you're missing some dependencies, nstool ('make assets', or
'make' under tests/), or similar.

There's a test/README.md file listing most dependencies and also
describing how to debug things, essentially:

  DEBUG=1 ./run

and have a look at script.log. Patches for whatever issue you
might be hitting in your setup are warmly welcome, of course. :)

-- 
Stefano


      reply	other threads:[~2025-06-11  8:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-20 15:09 vhost-kernel net on pasta: from 26 to 37Gbit/s Eugenio Perez Martin
2025-05-21  0:57 ` Jason Wang
2025-05-21  5:37   ` Eugenio Perez Martin
2025-05-21 10:08 ` Stefano Brivio
2025-05-21 10:35   ` Eugenio Perez Martin
2025-06-06 14:32     ` Eugenio Perez Martin
2025-06-06 16:37       ` Stefano Brivio
2025-06-09  9:59         ` Eugenio Perez Martin
2025-06-10 15:29           ` Stefano Brivio
2025-06-11  7:04             ` Eugenio Perez Martin
2025-06-11  8:08               ` Stefano Brivio [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=20250611100816.71bbf48a@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jenelson@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=pholzing@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).