Looks good, thanks! However, we should add the same control for the at line 1860.
netmap: use safer defaults for hwbuf_len
netmap: make sure rings are disabled during resets
Thanks, but the commit looks a bit strange: we are treating the pdev as a bus_dma_tag_t when it's really a pointer to a netmap adapter. It is not used at all on FreeBSD so it doesn't really matter, but maybe I'm missing something.
netmap: don't use linux type struct device *
Usage of "struct device *" was just wrong. Thanks spotting the issue.
Commit 70275a6735df8a514f48be77418491f2f8dba817 should have the same effect.
vmaffione retitled
D29697: remove IFNET_RLOCK() that collides CTX_LOCK() in iflib_netmap_register from
remove no ifnet_lock that collides CTX_LOCK in iflib_netmap_register to
remove IFNET_RLOCK() that collides CTX_LOCK() in iflib_netmap_register.
netmap: vtnet: remove unused variable
netmap: vtnet: add support for netmap offsets
netmap: pkt-gen: allow -Z and -z to be used together
netmap: pkt-gen: allow -Z and -z to be used together
netmap: bridge: fix transmission in busy-wait mode
netmap: bridge: fix transmission in busy-wait mode
netmap: iflib: add nm_config callback
netmap: iflib: add nm_config callback
iflib: add support for netmap offsets
netmap: update unit tests with libnetmap tests
libnetmap: reset errno in nmreq_register_decode()
netmap: restore commit a56e6334d1b7ed6e6faaa8b4612d948005ba74f5
netmap: several typo fixes
netmap: fix typo bug in netmap_compute_buf_len
libnetmap: restore changes in 26c29e743bbdbb82762540f72d4bc449bae2e092
netmap: bridge: fix transmission in busy-wait mode
netmap: pkt-gen: allow -Z and -z to be used together
Now that libnetmap has been merged and valectl updated, we can apply part of this change (documentation, usage, error checking).
libnetmap: add support for the offset features
netmap: monitor: add a flag to distinguish packet direction
netmap: add kernel support for the "offsets" feature
netmap: iflib: add nm_config callback
netmap: fix issues in nm_os_extmem_create()
netmap: fix memory leak in NETMAP_REQ_PORT_INFO_GET
netmap: fix issues in nm_os_extmem_create()
netmap: fix issues in nm_os_extmem_create()
netmap: fix issues in nm_os_extmem_create()
Forgot to link the commit to this review.
netmap: fix issues in nm_os_extmem_create()
Il giorno ven 19 mar 2021 alle ore 18:24 markj (Mark Johnston) <
phabric-noreply@freebsd.org> ha scritto:
Addressed reviewer comments
netmap: fix memory leak in NETMAP_REQ_PORT_INFO_GET
netmap: fix memory leak in NETMAP_REQ_PORT_INFO_GET
netmap: fix memory leak in NETMAP_REQ_PORT_INFO_GET
netmap: fix memory leak in NETMAP_REQ_PORT_INFO_GET
It may also help to use these commands (available on freefall) to look for style issues
Update my PGP key (using addkey.sh)
netmap: simplify parameter passing
iflib: netmap: move per-packet operation out of fragments loop
iflib: netmap: add support for NS_MOREFRAG
netmap: simplify parameter passing
iflib: netmap: move per-packet operation out of fragments loop
iflib: netmap: add support for NS_MOREFRAG
axgbe: fix some link related issues
netmap: simplify parameter passing
iflib: netmap: move per-packet operation out of fragments loop
iflib: netmap: add support for NS_MOREFRAG
iflib: add assert to prevent out-of-bounds array access
It can be merged there (MFC'd) as well, after a period of a minimum of 3 days. There is no need to submit a separate patch.
axgbe: fix some link related issues
Will the fix be provided as a firmware upgrade or how?
I could commit this change if you don't have someone else around that can do that for you.
Wouldn't it be easier to always perform the complete phy reset if this is a known hardware issue? Or maye perform it automatically after a normal reset does not work?
I'm afraid that adding an obscure sysctl (obscure for anyone except for the axgbe developers) would be of little use. Unaware users wouldn't have a clue about what to do...
just my 2 cents
re: netmap: enable/disable krings on interface reinit
netmap: vtnet: stop krings during interface reset
netmap: iflib: stop krings during interface reset
axgbe: driver changes for netmap support
netmap: pkt-gen: fix offset hex formatting
Shall I commit this change?
I added some comments, mostly about readability.
If you tested all the valid combinations of sph_enable and netmap/non-netmap I don't have any objection in this being merged.
netmap: pkt-gen: fix offset hex formatting
netmap: vtnet: fix RX initialization after netmap_reset()
netmap: restore hwofs and support it in iflib
re: netmap: enable/disable krings on interface reinit
iflib: fix build failure in case DEV_NETMAP is not defined
Il giorno dom 10 gen 2021 alle ore 13:20 rajesh1.kumar_amd.com (Rajesh
Kumar) <phabric-noreply@freebsd.org> ha scritto:
netmap: vtnet: enable/disable krings on any interface reinit
iflib: add assert to prevent out-of-bounds array access
netmap: iflib: enable/disable krings on any interface reinit
netmap: bridge: fix NS_MOREFRAG support
netmap: vtnet: stop krings during interface reset
netmap: refactor netmap_reset
netmap: iflib: fix asserts in netmap_fl_refill()
netmap: iflib: stop krings during interface reset
Thanks to both for the clarification.