public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: "Eugenio Pérez" <eperezma@redhat.com>,
	passt-dev@passt.top, jmaloy@redhat.com, lvivier@redhat.com,
	dgibson@redhat.com
Subject: Re: [PATCH 2/3] tap: implement vhost_call_cb
Date: Thu, 3 Apr 2025 12:48:42 +1100	[thread overview]
Message-ID: <Z-3o-sSROGNOqFP5@zatzit> (raw)
In-Reply-To: <20250402091622.7cda67ba@elisabeth>

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

On Wed, Apr 02, 2025 at 09:16:22AM +0200, Stefano Brivio wrote:
[snip]
> >  static int tap_ns_tun(void *arg)
> >  {
> > +	/* TODO we need to check if vhost support VIRTIO_NET_F_MRG_RXBUF and VHOST_NET_F_VIRTIO_NET_HDR actually */
> > +	static const uint64_t features =
> > +		(1ULL << VIRTIO_F_VERSION_1) | (1ULL << VIRTIO_NET_F_MRG_RXBUF) | (1ULL << VHOST_NET_F_VIRTIO_NET_HDR);
> >  	struct ifreq ifr = { .ifr_flags = IFF_TAP | IFF_NO_PI };
> 
> I kind of wonder, by the way, if IFF_TUN simplifies things here. It's
> something we should already add, as an option, see also:
> https://bugs.passt.top/show_bug.cgi?id=49, but if it makes your life
> easier for any reason you might consider adding it right away.

I agree that supporting IFF_TUN would be a good idea in general.  I
think trying to do it in the middle of this will be unnecessary
difficulty though.  There are a bunch of places throughout the code
that assume we have Ethernet headers, and changing that will require a
pretty wide ranging rework.

-- 
David Gibson (he or they)	| 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 --]

  parent reply	other threads:[~2025-04-03  1:51 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
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 [this message]
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=Z-3o-sSROGNOqFP5@zatzit \
    --to=david@gibson.dropbear.id.au \
    --cc=dgibson@redhat.com \
    --cc=eperezma@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).