public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Mina Almasry <almasrymina@google.com>
Cc: netdev@vger.kernel.org, Zinc Lim <zinclim@meta.com>, willemb@google.com
Subject: Re: fbnic qemu is open source
Date: Tue, 17 Mar 2026 14:34:46 -0700	[thread overview]
Message-ID: <20260317143446.4afabb97@kernel.org> (raw)
In-Reply-To: <CAHS8izMBx3j1nJwJ=b+ctGoJuEgTtMx8WsH2y-W=Sine+wo_3Q@mail.gmail.com>

On Tue, 17 Mar 2026 12:41:39 -0700 Mina Almasry wrote:
> > No plans at this stage to upstream it to QEMU because TBH I don't
> > expect that QEMU would care to carry random HW emulation drivers.
> >
> > Sorry if the announcement is a bit self-serving but folks expressed
> > interest off list in being able to test the queue API and zero-copy
> > Rx without real HW so I thought it's relevant.  
> 
> Wow, very cool! (Sorry I missed this announcement initially) I'm a bit
> of a noob but I'm a bit surprised a 'real' driver can work no qemu
> with a bit of magic.
> 
> Is fbnic-on-qemu about as feature-rich as fbnic-on-real-hardware? Do
> most of what it can do on real hardware it can do on qemu, or is it
> just really zerocopy that fully works?

We implement the driver and QEMU side by side pre-silicon so the QEMU
should cover what the driver can do. Keep in mind it's a pretty simple
NIC, even "in the flesh".

  reply	other threads:[~2026-03-17 21:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09 18:38 fbnic qemu is open source Jakub Kicinski
2026-03-17 19:41 ` Mina Almasry
2026-03-17 21:34   ` Jakub Kicinski [this message]
2026-03-17 21:42     ` Adam Young

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=20260317143446.4afabb97@kernel.org \
    --to=kuba@kernel.org \
    --cc=almasrymina@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.com \
    --cc=zinclim@meta.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox