public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Jon Maloy <jmaloy@redhat.com>
Cc: passt-dev@passt.top, lvivier@redhat.com, dgibson@redhat.com
Subject: Re: [PATCH v3 0/2] tcp: unify IPv4 and IPv6 tap queues
Date: Tue, 24 Sep 2024 22:30:29 +0200	[thread overview]
Message-ID: <20240924223029.08626c71@elisabeth> (raw)
In-Reply-To: <20240919184409.3511070-1-jmaloy@redhat.com>

On Thu, 19 Sep 2024 14:44:07 -0400
Jon Maloy <jmaloy@redhat.com> wrote:

> This should save us some memory and code.
> 
> ---
> v2: - Setting pointers to pre-set IP and MAC headers on the fly
>       instead of copying them.
>     - Merged patch #2 and #3 from v1
> v3: - Changes based on feedback from team

Sorry for the delay, now tests go a bit further but I have a similar
problem as I had on v2: guest to host, IPv6, with 65520 bytes MTU only
(perf/passt_tcp case), the iperf3 server fails to receive results, test
suite output:

=== perf/passt_tcp
> passt: throughput and latency
Throughput in Gbps, latency in µs, 4 threads at 3.6 GHz
                                        MTU: |  256B  |  576B  |  1280B |  1500B |  9000B | 65520B |
                                             |--------|--------|--------|--------|--------|--------|
   TCP throughput over IPv6: guest to host   |      - |      - |    5.8 |    6.5 |   18.1 |

and matching iperf3 server output:

- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate
[  6]   0.00-1.01   sec   568 MBytes  4.74 Gbits/sec                  receiver
[  9]   0.00-1.01   sec   621 MBytes  5.18 Gbits/sec                  receiver
[ 11]   0.00-1.01   sec   569 MBytes  4.75 Gbits/sec                  receiver
[ 13]   0.00-1.01   sec   675 MBytes  5.63 Gbits/sec                  receiver
[SUM]   0.00-1.01   sec  2.38 GBytes  20.3 Gbits/sec                  receiver
iperf3: error - unable to receive results: Bad file descriptor

after that, connectivity from the guest seems to be pretty much gone.
I didn't debug further.

-- 
Stefano


  parent reply	other threads:[~2024-09-24 20:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-19 18:44 [PATCH v3 0/2] tcp: unify IPv4 and IPv6 tap queues Jon Maloy
2024-09-19 18:44 ` [PATCH v3 1/2] tcp: set ip and eth headers in l2 tap queues on the fly Jon Maloy
2024-09-20  4:20   ` David Gibson
2024-09-19 18:44 ` [PATCH v3 2/2] tcp: unify l2 TCPv4 and TCPv6 queues and structures Jon Maloy
2024-09-20  4:52   ` David Gibson
2024-09-24 20:30 ` Stefano Brivio [this message]
2024-09-25  0:00   ` [PATCH v3 0/2] tcp: unify IPv4 and IPv6 tap queues Jon Maloy

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=20240924223029.08626c71@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=dgibson@redhat.com \
    --cc=jmaloy@redhat.com \
    --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).