From: Stephen Hemminger <stephen@networkplumber.org>
To: Mit Matelske <mit@pt.net>
Cc: shahafs <shahafs@mellanox.com>,
Thomas Monjalon <thomas@monjalon.net>, dev <dev@dpdk.org>,
Yongseok Koh <yskoh@mellanox.com>
Subject: Re: [dpdk-dev] mlx5 under FreeBSD
Date: Wed, 21 Nov 2018 12:12:04 -0800 [thread overview]
Message-ID: <20181121121204.297ef328@xeon-e3> (raw)
In-Reply-To: <1145619802.1261333.1542820311675.JavaMail.zimbra@perftech.com>
On Wed, 21 Nov 2018 11:11:51 -0600 (CST)
Mit Matelske <mit@pt.net> wrote:
> >
> > Rather than building a complex shim, why not just have an OS dependent section
> > of the driver. The bigger issue is that the kernel side functionality in BSD
> > is different or missing. For example TAP API is different and not multi-queue.
>
> Once I started working on it, I had to go this route. I haven't been able to but much
> time into it yet, but it is coming along:
>
> EAL: PCI device 0000:b3:00.0 on NUMA socket 0
> EAL: probe driver: 15b3:1013 net_mlx5
> net_mlx5: mlx5.c:1315: mlx5_pci_probe(): checking device "mlx5_0" uverbs0 /sys/class/infiniband_verbs/uverbs0 /sys/class/infiniband/mlx5_0
> net_mlx5: mlx5.c:1325: mlx5_pci_probe(): PCI information matches for device "mlx5_0"
> net_mlx5: mlx5.c:1315: mlx5_pci_probe(): checking device "mlx5_1" uverbs1 /sys/class/infiniband_verbs/uverbs1 /sys/class/infiniband/mlx5_1
> net_mlx5: mlx5.c:1382: mlx5_pci_probe(): no switch support detected
> net_mlx5: mlx5.c:796: mlx5_dev_spawn(): MPW isn't supported
> net_mlx5: mlx5.c:852: mlx5_dev_spawn(): tunnel offloading disabled due to old OFED/rdma-core version
> net_mlx5: mlx5.c:864: mlx5_dev_spawn(): MPLS over GRE/UDP tunnel offloading disabled due to old OFED/rdma-core version or firmware configuration
> net_mlx5: mlx5.c:877: mlx5_dev_spawn(): naming Ethernet device "0000:b3:00.0"
> net_mlx5: mlx5.c:1007: mlx5_dev_spawn(): checksum offloading is supported
> net_mlx5: mlx5.c:1024: mlx5_dev_spawn(): maximum Rx indirection table size is 512
> net_mlx5: mlx5.c:1028: mlx5_dev_spawn(): VLAN stripping is not supported
> net_mlx5: mlx5.c:1032: mlx5_dev_spawn(): FCS stripping configuration is not supported
> net_mlx5: mlx5.c:1037: mlx5_dev_spawn(): hardware Rx end alignment padding is not supported
> net_mlx5: mlx5.c:1052: mlx5_dev_spawn(): MPS is disabled
> net_mlx5: mlx5.c:628: mlx5_uar_init_primary(): port 0 reserved UAR address space: 0x880000000
> net_mlx5: mlx5.c:1107: mlx5_dev_spawn(): port 0 MAC address is 00:90:0b:78:2a:ea
> net_mlx5: mlx5.c:1114: mlx5_dev_spawn(): port 0 ifname is "mce0"
> net_mlx5: mlx5.c:1127: mlx5_dev_spawn(): port 0 MTU is 1500
> net_mlx5: mlx5.c:1142: mlx5_dev_spawn(): flow rules relying on switch offloads will not be supported: cannot open libmnl socket: Address family not supported by protocol family
> net_mlx5: mlx5.c:1176: mlx5_dev_spawn(): port 0 forcing Ethernet interface up
> net_mlx5: mlx5_ethdev.c:735: mlx5_link_update_unlocked_gs(): port 0 ioctl(SIOCGIFFLAGS) failed: No such file or directory
> net_mlx5: mlx5_ethdev.c:664: mlx5_link_update_unlocked_gset(): port 0 ioctl(SIOCGIFFLAGS) failed: No such file or directory
> net_mlx5: mlx5_rxq.c:2150: mlx5_hrxq_drop_new(): port 0 cannot allocate QP for drop queue
> Segmentation fault (core dumped)
>
> Working through mlx5_ethdev now...
>
> Mit
Also if you are targeting Azure or Hyper-V, then don't bother porting TAP/VDEV_NETVSC/Failsafe model
because that is being replaced by netvsc native PMD. It would be easier to just get that working.
It would mean writing a uio equivalent driver for FreeBSD.
next prev parent reply other threads:[~2018-11-21 20:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 16:48 Mit Matelske
2018-11-18 14:38 ` Thomas Monjalon
2018-11-18 23:23 ` Mit Matelske
2018-11-19 6:28 ` Shahaf Shuler
2018-11-19 15:09 ` Mit Matelske
2018-11-19 17:08 ` Stephen Hemminger
2018-11-21 17:11 ` Mit Matelske
2018-11-21 20:12 ` Stephen Hemminger [this message]
2019-03-01 15:58 ` Mit Matelske
2019-03-03 8:43 ` Shahaf Shuler
2019-03-04 16:44 ` Mit Matelske
2019-03-06 14:59 ` Shahaf Shuler
2019-03-06 21:01 ` Mit Matelske
2019-03-07 6:28 ` Shahaf Shuler
2019-03-07 15:27 ` Mit Matelske
2019-03-10 5:57 ` Shahaf Shuler
2019-03-11 14:29 ` Mit Matelske
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=20181121121204.297ef328@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=mit@pt.net \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.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).