<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src/tests/sys/netmap, branch releng/12.4</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.4</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src/atom?h=releng%2F12.4'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/'/>
<updated>2021-08-29T13:28:30Z</updated>
<entry>
<title>Revert "Do a sweep and remove most WARNS=6 settings"</title>
<updated>2021-08-29T13:28:30Z</updated>
<author>
<name>Dimitry Andric</name>
<email>dim@FreeBSD.org</email>
</author>
<published>2021-08-29T13:28:30Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=e92630fc682954a7b4f724f4a8174d196d7d9cc5'/>
<id>urn:sha1:e92630fc682954a7b4f724f4a8174d196d7d9cc5</id>
<content type='text'>
This reverts commit befc47822966, as it caused various CI build errors,
and we never merged the prerequisite commit fe815331bb40 ("build:
provide a default WARNS for all in-tree builds"). The latter is rather
intrusive, so I will avoid it.

Direct commit to stable/12 since the CI bots are broken.
</content>
</entry>
<entry>
<title>Do a sweep and remove most WARNS=6 settings</title>
<updated>2021-08-29T10:49:28Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2020-10-01T01:10:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=befc478229660bca9cbda38d73f6b9d7c8918ded'/>
<id>urn:sha1:befc478229660bca9cbda38d73f6b9d7c8918ded</id>
<content type='text'>
Repeating the default WARNS here makes it slightly more difficult to
experiment with default WARNS changes, e.g. if we did something absolutely
bananas and introduced a WARNS=7 and wanted to try lifting the default to
that.

Drop most of them; there is one in the blake2 kernel module, but I suspect
it should be dropped -- the default WARNS in the rest of the build doesn't
currently apply to kernel modules, and I haven't put too much thought into
whether it makes sense to make it so.

(cherry picked from commit 7cc42f6d25ef2e19059d088fa7d4853fe9afefb5)
</content>
</entry>
<entry>
<title>MFC r346184</title>
<updated>2019-06-02T18:46:21Z</updated>
<author>
<name>Vincenzo Maffione</name>
<email>vmaffione@FreeBSD.org</email>
</author>
<published>2019-06-02T18:46:21Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=06a67b22e8b551e94ec4efce1912c441bc7f0330'/>
<id>urn:sha1:06a67b22e8b551e94ec4efce1912c441bc7f0330</id>
<content type='text'>
netmap: add test cases for multiple host rings

Extend the netmap unit tests with new test cases for the multiple-host-rings
feature introduced by r345269.
</content>
</entry>
<entry>
<title>MFC r345644,r346061:</title>
<updated>2019-04-16T01:03:38Z</updated>
<author>
<name>Enji Cooper</name>
<email>ngie@FreeBSD.org</email>
</author>
<published>2019-04-16T01:03:38Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=05e2b30132ec72b43d409d40cb7df0d9543cfc8e'/>
<id>urn:sha1:05e2b30132ec72b43d409d40cb7df0d9543cfc8e</id>
<content type='text'>
r345644 (by olivier):

Skip this test if if_tap module is not available

PR:		236842

r346061:

Polish netmap(4) testcases a bit

1. Not all kernels have netmap(4) support. Check for netmap(4) support before
   attempting to run the tests via the `PLAIN_REQUIRE_KERNEL_MODULE(..)` macro.
2. Libraries shouldn't be added to LDFLAGS; they should be added to LIBADD
   instead. This allows the build system to evaluate dependencies for sanity.
3. Sort some of the Makefile variables per bsd.README.

1., in particular, will resolve failures when running this testcase on kernels
lacking netmap(4) support, e.g., the i386 GENERIC kernels on ^/stable/11 and
^/stable/12.

PR:		237129
</content>
</entry>
<entry>
<title>MFC r345269, r345323</title>
<updated>2019-04-01T10:51:24Z</updated>
<author>
<name>Vincenzo Maffione</name>
<email>vmaffione@FreeBSD.org</email>
</author>
<published>2019-04-01T10:51:24Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=7af42e831191452c43cd97317624361b43125f3d'/>
<id>urn:sha1:7af42e831191452c43cd97317624361b43125f3d</id>
<content type='text'>
netmap: add support for multiple host rings

Some applications forward from/to host rings most or all the
traffic received or sent on a physical interface. In this
cases it is desirable to have more than a pair of RX/TX host
rings, and use multiple threads to speed up forwarding.
This change adds support for multiple host rings. On registering
a netmap port, the user can specify the number of desired receive
and transmit host rings in the nr_host_tx_rings and nr_host_rx_rings
fields of the nmreq_register structure.
</content>
</entry>
<entry>
<title>MFC r342737</title>
<updated>2019-01-10T08:52:50Z</updated>
<author>
<name>Vincenzo Maffione</name>
<email>vmaffione@FreeBSD.org</email>
</author>
<published>2019-01-10T08:52:50Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=7c72d86998a627e04f55c24e074b45d3d8168213'/>
<id>urn:sha1:7c72d86998a627e04f55c24e074b45d3d8168213</id>
<content type='text'>
netmap: unit tests: fix issues found by coverity scan

Reported by:    asomers
Sponsored by:   Sunny Valley Networks
</content>
</entry>
<entry>
<title>MFC r342649, r342650</title>
<updated>2019-01-08T09:40:09Z</updated>
<author>
<name>Vincenzo Maffione</name>
<email>vmaffione@FreeBSD.org</email>
</author>
<published>2019-01-08T09:40:09Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src/commit/?id=1b1076c4254a5134ef59fa3a04b5cf2a1a4c4871'/>
<id>urn:sha1:1b1076c4254a5134ef59fa3a04b5cf2a1a4c4871</id>
<content type='text'>
netmap: add suite of unit tests

Import the unit tests from upstream (https://github.com/luigirizzo/netmap
ba02539859d46d33), and make them ready for use with Kyua.
There are currently 38 regression tests, which test the kernel control ABI
exposed by netmap to userspace applications:

  1: test for port info get
  2-5: tests for basic port registration
  6-9: tests for VALE
  10-11: tests for getting netmap allocator info
  12-15: tests for netmap pipes
  16: test on polling mode
  17-18: tests on options
  19-27: tests for sync-kloop subsystem
  28-39: tests for null ports
  31-38: tests for the legacy NIOCREGIF registers

Reviewed by:    ngie
Sponsored by:	Sunny Valley Networks
Differential Revision:  https://reviews.freebsd.org/D18490
</content>
</entry>
</feed>
