netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: netdev@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, Russell King <linux@armlinux.org.uk>,
	Sanman Pradhan <sanmanpradhan@meta.com>,
	Andrew Lunn <andrew@lunn.ch>,
	Alexander Duyck <alexanderduyck@fb.com>,
	davem@davemloft.net, pabeni@redhat.com, edumazet@google.com,
	kernel-team@meta.com
Subject: Re: [net-next PATCH v4 00/15] eth: fbnic: Add network driver for Meta Platforms Host Network Interface
Date: Wed, 10 Jul 2024 11:12:10 -0700	[thread overview]
Message-ID: <20240710111210.0d9bea99@kernel.org> (raw)
In-Reply-To: <172054602727.1305884.10973465571854855750.stgit@ahduyck-xeon-server.home.arpa>

On Tue, 09 Jul 2024 10:28:30 -0700 Alexander Duyck wrote:
> This patchest includes the necessary patches to enable basic Tx and Rx over
> the Meta Platforms Host Network Interface. To do this we introduce a new
> driver and driver directories in the form of
> "drivers/net/ethernet/meta/fbnic".
> 
> The NIC itself is fairly simplistic. As far as speeds we support 25Gb,
> 50Gb, and 100Gb and we are mostly focused on speeds and feeds. As far as
> future patch sets we will be supporting the basic Rx/Tx offloads such as
> header/payload data split, TSO, checksum, and timestamp offloads. We have
> access to the MAC and PCS from the NIC, however the PHY and QSFP are hidden
> behind a FW layer as it is shared between 4 slices and the BMC.
> 
> Due to submission limits the the general plan to submit a minimal driver
> for now almost equivilent to a UEFI driver in functionality, and then
> follow up over the coming months enabling additional offloads and enabling
> more features for the device.

cocci says:

drivers/net/ethernet/meta/fbnic/fbnic_irq.c:42:7-27: WARNING: Threaded IRQ with no primary handler requested without IRQF_ONESHOT (unless it is nested IRQ)
-- 
pw-bot: cr

  parent reply	other threads:[~2024-07-10 18:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-09 17:28 [net-next PATCH v4 00/15] eth: fbnic: Add network driver for Meta Platforms Host Network Interface Alexander Duyck
2024-07-09 17:28 ` [net-next PATCH v4 01/15] PCI: Add Meta Platforms vendor ID Alexander Duyck
2024-07-09 17:28 ` [net-next PATCH v4 02/15] eth: fbnic: Add scaffolding for Meta's NIC driver Alexander Duyck
2024-07-09 17:28 ` [net-next PATCH v4 03/15] eth: fbnic: Allocate core device specific structures and devlink interface Alexander Duyck
2024-07-09 17:28 ` [net-next PATCH v4 04/15] eth: fbnic: Add register init to set PCIe/Ethernet device config Alexander Duyck
2024-07-09 17:28 ` [net-next PATCH v4 05/15] eth: fbnic: Add message parsing for FW messages Alexander Duyck
2024-07-09 17:28 ` [net-next PATCH v4 06/15] eth: fbnic: Add FW communication mechanism Alexander Duyck
2024-07-09 17:28 ` [net-next PATCH v4 07/15] eth: fbnic: Allocate a netdevice and napi vectors with queues Alexander Duyck
2024-07-09 17:29 ` [net-next PATCH v4 08/15] eth: fbnic: Implement Tx queue alloc/start/stop/free Alexander Duyck
2024-07-09 17:29 ` [net-next PATCH v4 09/15] eth: fbnic: Implement Rx " Alexander Duyck
2024-07-09 17:29 ` [net-next PATCH v4 10/15] eth: fbnic: Add initial messaging to notify FW of our presence Alexander Duyck
2024-07-09 17:29 ` [net-next PATCH v4 11/15] eth: fbnic: Add link detection Alexander Duyck
2024-07-09 17:29 ` [net-next PATCH v4 12/15] eth: fbnic: Add basic Tx handling Alexander Duyck
2024-07-09 17:29 ` [net-next PATCH v4 13/15] eth: fbnic: Add basic Rx handling Alexander Duyck
2024-07-09 17:29 ` [net-next PATCH v4 14/15] eth: fbnic: Add L2 address programming Alexander Duyck
2024-07-09 17:29 ` [net-next PATCH v4 15/15] eth: fbnic: Write the TCAM tables used for RSS control and Rx to host Alexander Duyck
2024-07-10 18:12 ` Jakub Kicinski [this message]
2024-07-10 23:51   ` [net-next PATCH v4 00/15] eth: fbnic: Add network driver for Meta Platforms Host Network Interface Alexander Duyck

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=20240710111210.0d9bea99@kernel.org \
    --to=kuba@kernel.org \
    --cc=alexander.duyck@gmail.com \
    --cc=alexanderduyck@fb.com \
    --cc=andrew@lunn.ch \
    --cc=bhelgaas@google.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kernel-team@meta.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sanmanpradhan@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;
as well as URLs for NNTP newsgroup(s).