public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Eugenio Perez Martin <eperezma@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, jmaloy@redhat.com, sbrivio@redhat.com,
	lvivier@redhat.com, dgibson@redhat.com
Subject: Re: [PATCH 1/3] tap: specify the packet pool
Date: Thu, 3 Apr 2025 08:40:56 +0200	[thread overview]
Message-ID: <CAJaqyWdxWXqcxXb2EU7AQrWdiF1SSHa6_0_By1hORpkZfggmUg@mail.gmail.com> (raw)
In-Reply-To: <Z-3fbVJnOdOVr8Wm@zatzit>

On Thu, Apr 3, 2025 at 3:51 AM David Gibson <david@gibson.dropbear.id.au> wrote:
>
> On Tue, Apr 01, 2025 at 01:38:07PM +0200, Eugenio Pérez wrote:
> > In vhost-kernel we need to allocate a storage for rx so kernel can
> > write the buffers async. We need to tell tap_add_packet where to find
> > them.
> >
> > Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
>
> As discussed on our call, I don't think we need this.  We should be
> able to re-use pool_tap[46] for vhost-net.
>

Right, I'm able to transmit from the guest reusing pool_tap[46] now, thanks!


  reply	other threads:[~2025-04-03  6:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-01 11:38 [PATCH 0/3] Add vhost-net kernel support Eugenio Pérez
2025-04-01 11:38 ` [PATCH 1/3] tap: specify the packet pool Eugenio Pérez
2025-04-03  1:07   ` David Gibson
2025-04-03  6:40     ` Eugenio Perez Martin [this message]
2025-04-01 11:38 ` [PATCH 2/3] tap: implement vhost_call_cb Eugenio Pérez
2025-04-02  7:16   ` Stefano Brivio
2025-04-02 12:03     ` Eugenio Perez Martin
2025-04-03  1:48     ` David Gibson
2025-04-03  4:28       ` Stefano Brivio
2025-04-03  1:45   ` David Gibson
2025-04-01 11:38 ` [PATCH 3/3] tap: add die() on vhost error Eugenio Pérez
2025-04-03  1:50   ` David Gibson
2025-04-03  6:36     ` Eugenio Perez Martin

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=CAJaqyWdxWXqcxXb2EU7AQrWdiF1SSHa6_0_By1hORpkZfggmUg@mail.gmail.com \
    --to=eperezma@redhat.com \
    --cc=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).