<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test/usr.bin/systat/netstat.c, branch releng/11.2</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test/atom?h=releng%2F11.2</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test/atom?h=releng%2F11.2'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/'/>
<updated>2018-03-29T02:50:57Z</updated>
<entry>
<title>Revert r330897:</title>
<updated>2018-03-29T02:50:57Z</updated>
<author>
<name>Eitan Adler</name>
<email>eadler@FreeBSD.org</email>
</author>
<published>2018-03-29T02:50:57Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=4ab2e064d7950be84256d671a7ae93f87cc6aa36'/>
<id>urn:sha1:4ab2e064d7950be84256d671a7ae93f87cc6aa36</id>
<content type='text'>
This was intended to be a non-functional change. It wasn't. The commit
message was thus wrong. In addition it broke arm, and merged crypto
related code.

Revert with prejudice.

This revert skips files touched in r316370 since that commit was since
MFCed. This revert also skips files that require $FreeBSD$ property
changes.

Thank you to those who helped me get out of this mess including but not
limited to gonzo, kevans, rgrimes.

Requested by: gjb (re)
</content>
</entry>
<entry>
<title>Partial merge of the SPDX changes</title>
<updated>2018-03-14T03:19:51Z</updated>
<author>
<name>Eitan Adler</name>
<email>eadler@FreeBSD.org</email>
</author>
<published>2018-03-14T03:19:51Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=be5d0b9566b13fdf8cabebb63334cbec12bfc409'/>
<id>urn:sha1:be5d0b9566b13fdf8cabebb63334cbec12bfc409</id>
<content type='text'>
These changes are incomplete but are making it difficult
to determine what other changes can/should be merged.

No objections from:	pfg
</content>
</entry>
<entry>
<title>Use NULL instead of 0 for pointers.</title>
<updated>2016-04-20T01:26:03Z</updated>
<author>
<name>Marcelo Araujo</name>
<email>araujo@FreeBSD.org</email>
</author>
<published>2016-04-20T01:26:03Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=61c2ed541de842f3d2931bb87c877656a6710bf3'/>
<id>urn:sha1:61c2ed541de842f3d2931bb87c877656a6710bf3</id>
<content type='text'>
gethostbyname(3) will return NULL for error status.

MFC after:	2 weeks.
</content>
</entry>
<entry>
<title>Augment struct tcpstat with tcps_states[], which is used for book-keeping</title>
<updated>2016-01-27T00:45:46Z</updated>
<author>
<name>Gleb Smirnoff</name>
<email>glebius@FreeBSD.org</email>
</author>
<published>2016-01-27T00:45:46Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=57a78e3baeb583a817195e5aee153f6387b9b2b0'/>
<id>urn:sha1:57a78e3baeb583a817195e5aee153f6387b9b2b0</id>
<content type='text'>
the amount of TCP connections by state.  Provides a cheap way to get
connection count without traversing the whole pcb list.

Sponsored by:	Netflix
</content>
</entry>
<entry>
<title> - Avoid accessing window properties directly, instead, use accessors.</title>
<updated>2015-09-10T22:07:52Z</updated>
<author>
<name>Xin LI</name>
<email>delphij@FreeBSD.org</email>
</author>
<published>2015-09-10T22:07:52Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=1e902b3b7e30974a728218d406b509ec0d49e32b'/>
<id>urn:sha1:1e902b3b7e30974a728218d406b509ec0d49e32b</id>
<content type='text'>
   This should be no-op for now, but allows the code to work if we
   move to NCURSES_OPAQUE.
 - Use calloc() instead of malloc+bzero.

MFC after:	2 weeks
</content>
</entry>
<entry>
<title>Merge from projects/sendfile:</title>
<updated>2014-11-30T12:52:33Z</updated>
<author>
<name>Gleb Smirnoff</name>
<email>glebius@FreeBSD.org</email>
</author>
<published>2014-11-30T12:52:33Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=0f9d0a73a495b204ea02cf1da28db1bdd0c7e40b'/>
<id>urn:sha1:0f9d0a73a495b204ea02cf1da28db1bdd0c7e40b</id>
<content type='text'>
o Introduce a notion of "not ready" mbufs in socket buffers.  These
mbufs are now being populated by some I/O in background and are
referenced outside.  This forces following implications:
- An mbuf which is "not ready" can't be taken out of the buffer.
- An mbuf that is behind a "not ready" in the queue neither.
- If sockbet buffer is flushed, then "not ready" mbufs shouln't be
  freed.

o In struct sockbuf the sb_cc field is split into sb_ccc and sb_acc.
  The sb_ccc stands for ""claimed character count", or "committed
  character count".  And the sb_acc is "available character count".
  Consumers of socket buffer API shouldn't already access them directly,
  but use sbused() and sbavail() respectively.
o Not ready mbufs are marked with M_NOTREADY, and ready but blocked ones
  with M_BLOCKED.
o New field sb_fnrdy points to the first not ready mbuf, to avoid linear
  search.
o New function sbready() is provided to activate certain amount of mbufs
  in a socket buffer.

A special note on SCTP:
  SCTP has its own sockbufs.  Unfortunately, FreeBSD stack doesn't yet
allow protocol specific sockbufs.  Thus, SCTP does some hacks to make
itself compatible with FreeBSD: it manages sockbufs on its own, but keeps
sb_cc updated to inform the stack of amount of data in them.  The new
notion of "not ready" data isn't supported by SCTP.  Instead, only a
mechanical substitute is done: s/sb_cc/sb_ccc/.
  A proper solution would be to take away struct sockbuf from struct
socket and allow protocols to implement their own socket buffers, like
SCTP already does.  This was discussed with rrs@.

Sponsored by:	Netflix
Sponsored by:	Nginx, Inc.
</content>
</entry>
<entry>
<title>Whitespace fixes.</title>
<updated>2012-02-05T09:17:49Z</updated>
<author>
<name>Ed Schouten</name>
<email>ed@FreeBSD.org</email>
</author>
<published>2012-02-05T09:17:49Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=627d915e25e2dc7c9767bbeed2e945f1563763ed'/>
<id>urn:sha1:627d915e25e2dc7c9767bbeed2e945f1563763ed</id>
<content type='text'>
- Remove redundant empty lines.
- Replace ^L by \014. This allows you to safely cat/grep/etc this file
  without causing confusion.
</content>
</entry>
<entry>
<title>Replace index() and rindex() calls with strchr() and strrchr().</title>
<updated>2012-01-03T18:51:58Z</updated>
<author>
<name>Ed Schouten</name>
<email>ed@FreeBSD.org</email>
</author>
<published>2012-01-03T18:51:58Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=b3608ae18f1e5598bed81d0a10dd585a5080c40d'/>
<id>urn:sha1:b3608ae18f1e5598bed81d0a10dd585a5080c40d</id>
<content type='text'>
The index() and rindex() functions were marked LEGACY in the 2001
revision of POSIX and were subsequently removed from the 2008 revision.
The strchr() and strrchr() functions are part of the C standard.

This makes the source code a lot more consistent, as most of these C
files also call into other str*() routines. In fact, about a dozen
already perform strchr() calls.
</content>
</entry>
<entry>
<title>Fix whitespace inconsistencies in systat(1).</title>
<updated>2011-10-15T13:20:36Z</updated>
<author>
<name>Ed Schouten</name>
<email>ed@FreeBSD.org</email>
</author>
<published>2011-10-15T13:20:36Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=2bd338d6c4bb3419ca8e4ce46e3472f545df25a4'/>
<id>urn:sha1:2bd338d6c4bb3419ca8e4ce46e3472f545df25a4</id>
<content type='text'>
According to md5(1), the resulting binary is the same.
</content>
</entry>
<entry>
<title>Remove duplicated header files</title>
<updated>2011-06-24T07:18:44Z</updated>
<author>
<name>Kevin Lo</name>
<email>kevlo@FreeBSD.org</email>
</author>
<published>2011-06-24T07:18:44Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test/commit/?id=aa7e4bb4663ca1167a0c9de643091ffaffebdc4f'/>
<id>urn:sha1:aa7e4bb4663ca1167a0c9de643091ffaffebdc4f</id>
<content type='text'>
</content>
</entry>
</feed>
