<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test2/sys/dev/age, branch release/11.0.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.0.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.0.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/'/>
<updated>2016-04-26T15:03:15Z</updated>
<entry>
<title>sys/dev: extend use of the howmany() macro when available.</title>
<updated>2016-04-26T15:03:15Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2016-04-26T15:03:15Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=057b4402bf634907fd03590e2757e09e975d04c7'/>
<id>urn:sha1:057b4402bf634907fd03590e2757e09e975d04c7</id>
<content type='text'>
We have a howmany() macro in the &lt;sys/param.h&gt; header that is
convenient to re-use as it makes things easier to read.
</content>
</entry>
<entry>
<title>sys/dev: use our nitems() macro when it is avaliable through param.h.</title>
<updated>2016-04-19T23:37:24Z</updated>
<author>
<name>Pedro F. Giffuni</name>
<email>pfg@FreeBSD.org</email>
</author>
<published>2016-04-19T23:37:24Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=73a1170a8c41cb848f17cc0a8839e9dcee3d126e'/>
<id>urn:sha1:73a1170a8c41cb848f17cc0a8839e9dcee3d126e</id>
<content type='text'>
No functional change, only trivial cases are done in this sweep,
Drivers that can get further enhancements will be done independently.

Discussed in:	freebsd-current
</content>
</entry>
<entry>
<title>Fix variable assignment.</title>
<updated>2016-02-18T01:24:10Z</updated>
<author>
<name>Pyun YongHyeon</name>
<email>yongari@FreeBSD.org</email>
</author>
<published>2016-02-18T01:24:10Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=9dda5c8ffc7466f940ed2ae0b056c9ae39e3208a'/>
<id>urn:sha1:9dda5c8ffc7466f940ed2ae0b056c9ae39e3208a</id>
<content type='text'>
Found by:	PVS-Studio
</content>
</entry>
<entry>
<title>Mechanically convert to if_inc_counter().</title>
<updated>2014-09-18T21:01:41Z</updated>
<author>
<name>Gleb Smirnoff</name>
<email>glebius@FreeBSD.org</email>
</author>
<published>2014-09-18T21:01:41Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=1209989c6ae0d8dc6f4b74f6420e95a1e613af15'/>
<id>urn:sha1:1209989c6ae0d8dc6f4b74f6420e95a1e613af15</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Use define from if_var.h to access a field inside struct if_data,</title>
<updated>2014-08-30T19:55:54Z</updated>
<author>
<name>Gleb Smirnoff</name>
<email>glebius@FreeBSD.org</email>
</author>
<published>2014-08-30T19:55:54Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=1bffa9511fe94125820858b0ead796db54ac019d'/>
<id>urn:sha1:1bffa9511fe94125820858b0ead796db54ac019d</id>
<content type='text'>
that resides in struct ifnet.

Sponsored by:	Nginx, Inc.
</content>
</entry>
<entry>
<title>Fix various NIC drivers to properly cleanup static DMA resources.</title>
<updated>2014-06-11T14:53:58Z</updated>
<author>
<name>John Baldwin</name>
<email>jhb@FreeBSD.org</email>
</author>
<published>2014-06-11T14:53:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=068d8643adb13434b57fdd5febf43a11194d508f'/>
<id>urn:sha1:068d8643adb13434b57fdd5febf43a11194d508f</id>
<content type='text'>
In particular, don't check the value of the bus_dma map against NULL
to determine if either bus_dmamem_alloc() or bus_dmamap_load() succeeded.
Instead, assume that bus_dmamap_load() succeeeded (and thus that
bus_dmamap_unload() should be called) if the bus address for a resource
is non-zero, and assume that bus_dmamem_alloc() succeeded (and thus
that bus_dmamem_free() should be called) if the virtual address for a
resource is not NULL.

In many cases these bugs could result in leaks when a driver was detached.

Reviewed by:	yongari
MFC after:	2 weeks
</content>
</entry>
<entry>
<title>Increase the number of TX DMA segments from 32 to 35.  It turned</title>
<updated>2014-03-31T01:54:59Z</updated>
<author>
<name>Pyun YongHyeon</name>
<email>yongari@FreeBSD.org</email>
</author>
<published>2014-03-31T01:54:59Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=52ee8ac0274e8d4f75a146944803b2cdaad092bb'/>
<id>urn:sha1:52ee8ac0274e8d4f75a146944803b2cdaad092bb</id>
<content type='text'>
out 32 is not enough to support a full sized TSO packet.
While I'm here fix a long standing bug introduced in r169632 in
bce(4) where it didn't include L2 header length of TSO packet in
the maximum DMA segment size calculation.

In collaboration with:	rmacklem
MFC after:		2 weeks
</content>
</entry>
<entry>
<title>The r48589 promised to remove implicit inclusion of if_var.h soon. Prepare</title>
<updated>2013-10-26T17:58:36Z</updated>
<author>
<name>Gleb Smirnoff</name>
<email>glebius@FreeBSD.org</email>
</author>
<published>2013-10-26T17:58:36Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=76039bc84fae9915788b54ff28fe0cc4876952d2'/>
<id>urn:sha1:76039bc84fae9915788b54ff28fe0cc4876952d2</id>
<content type='text'>
to this event, adding if_var.h to files that do need it. Also, include
all includes that now are included due to implicit pollution via if_var.h

Sponsored by:	Netflix
Sponsored by:	Nginx, Inc.
</content>
</entry>
<entry>
<title>Be sure to actually decrement the "count" parameter for each processed</title>
<updated>2013-06-17T22:59:47Z</updated>
<author>
<name>Mark Johnston</name>
<email>markj@FreeBSD.org</email>
</author>
<published>2013-06-17T22:59:47Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=0203558fe6daac838b29d976327412feaee062f5'/>
<id>urn:sha1:0203558fe6daac838b29d976327412feaee062f5</id>
<content type='text'>
descriptor so that we return when the threshold has been reached.

Reviewed by:	yongari
MFC after:	1 week
</content>
</entry>
<entry>
<title>Rework jumbo frame handling.  QAC confirmed that the controller</title>
<updated>2013-02-05T00:37:45Z</updated>
<author>
<name>Pyun YongHyeon</name>
<email>yongari@FreeBSD.org</email>
</author>
<published>2013-02-05T00:37:45Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=088dd4b78a37c621a8427f067ecd3a2eb79b3471'/>
<id>urn:sha1:088dd4b78a37c621a8427f067ecd3a2eb79b3471</id>
<content type='text'>
requires 8 bytes alignment on RX buffer.  Given that non-jumbo
frame works on any alignments I guess this DMA limitation for RX
buffer could be jumbo frame specific one.  Also I'm not sure
whether this DMA limitation is related with 64bit DMA.  Previously
age(4) disabled 64bit DMA addressing due to silent data corruption.
So we may need more testing on re-enabling 64bit DMA in future.

While I'm here, change mbuf chaining algorithm to use fixed sized
buffer and force software checksum if controller reports length
error. According to QAC, RFD is not updated at all for jumbo frame
so it works just like alc(4) controllers.  This change also added
alignment fixup for strict alignment architectures.  Because I'm
not aware of any non-x86 machines that use age(4) controllers it's
just for completeness at this moment.

Wit this change, jumbo frame should work with age(4).

Tested by:	Christian Gusenbauer &lt; c47g &lt;&gt; gmx dot at &gt;
MFC after:	1 week
</content>
</entry>
</feed>
