| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
GIANT from VFS.
This is not targeted for MFC.
|
|
|
|
| |
Approved by: joel
|
|
|
|
|
|
|
| |
try to discourage users from depending on it.
Approved by: joel
MFC after: 3 days
|
| |
|
| |
|
|
|
|
|
| |
Submitted by: Dmitry Luhtionov <dmitryluhtionov at gmail.com>
MFC with: r241446
|
|
|
|
| |
Submitted by: brueffer
|
| |
|
| |
|
|
|
|
| |
NULL instead of 0 when dealing with pointers.
|
|
|
|
|
| |
Submitted by: Bryan Venteicher bryanv at daemoninthecloset dot org
Reviewed by: grehan
|
|
|
|
|
|
|
|
| |
in devices and mount paths, encoded as \s or \040.
PR: bin/117687
Submitted by: Martin Kammerhofer
Discussed on: arch
|
|
|
|
|
| |
Sponsored by: Intel
Reviewed by: joel
|
|
|
|
|
|
| |
MK_CTF is used internally).
Reviewed by: fjoe
|
|
|
|
| |
Pointyhat to: kevlo (myself)
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- All packets in NETISR_IP queue are in net byte order.
- ip_input() is entered in net byte order and converts packet
to host byte order right _after_ processing pfil(9) hooks.
- ip_output() is entered in host byte order and converts packet
to net byte order right _before_ processing pfil(9) hooks.
- ip_fragment() accepts and emits packet in net byte order.
- ip_forward(), ip_mloopback() use host byte order (untouched actually).
- ip_fastforward() no longer modifies packet at all (except ip_ttl).
- Swapping of byte order there and back removed from the following modules:
pf(4), ipfw(4), enc(4), if_bridge(4).
- Swapping of byte order added to ipfilter(4), based on __FreeBSD_version
- __FreeBSD_version bumped.
- pfil(9) manual page updated.
Reviewed by: ray, luigi, eri, melifaro
Tested by: glebius (LE), ray (BE)
|
|
|
|
|
|
|
| |
both boot (via loader tunables) and run-time (via `camcontrol negotiate`).
Tested to work at least on NVIDIA MCP55 chipset.
H/w provided by: glebius
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tree used it incorrectly, which lead to inaccurate overrated
if_obytes accounting. The drbr(9) used to update ifnet stats on
drbr_enqueue(), which is not accurate since enqueuing doesn't
imply successful processing by driver. Dequeuing neither mean
that. Most drivers also called drbr_stats_update() which did
accounting again, leading to doubled if_obytes statistics. And
in case of severe transmitting, when a packet could be several
times enqueued and dequeued it could have been accounted several
times.
o Thus, make drbr(9) API thinner. Now drbr(9) merely chooses between
ALTQ queueing or buf_ring(9) queueing.
- It doesn't touch the buf_ring stats any more.
- It doesn't touch ifnet stats anymore.
- drbr_stats_update() no longer exists.
o buf_ring(9) handles its stats itself:
- It handles br_drops itself.
- br_prod_bytes stats are dropped. Rationale: no one ever
reads them but update of a common counter on every packet
negatively affects performance due to excessive cache
invalidation.
- buf_ring_enqueue_bytes() reduced to buf_ring_enqueue(), since
we no longer account bytes.
o Drivers handle their stats theirselves: if_obytes, if_omcasts.
o mlx4(4), igb(4), em(4), vxge(4), oce(4) and ixv(4) no longer
use drbr_stats_update(), and update ifnet stats theirselves.
o bxe(4) was the most correct driver, it didn't call
drbr_stats_update(), thus it was the only driver accurate under
moderate load. Now it also maintains stats itself.
o ixgbe(4) had already taken stats from hardware, so just
- drop software stats updating.
- take multicast packet count from hardware as well.
o mxge(4) just no longer needs NO_SLOW_STATS define.
o cxgb(4), cxgbe(4) need no change, since they obtain stats
from hardware.
Reviewed by: jfv, gnn
|
|
|
|
|
|
| |
sentence on a new line.
Approved by: hrs (mentor)
|
|
|
|
| |
Submitted by: Dmitry Luhtionov <dmitryluhtionov@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
While here increase the suggested sizes for the
partition as "make universe" takes a lot more
space than mentioned.
Reviewed by: gavin
Approved by: gjb
MFC after: 3 days
X-MFC-With: r240728
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
in the world of subversion.
Approved by: gjb
MFC after: 2 weeks
|
| |
|
|
|
|
| |
Approved by: joel (mentor)
|
|
|
|
|
|
| |
PR: bin/171767
Submitted by: zeising
Approved by: joel (mentor), glebius
|
|
|
|
|
|
|
|
| |
This is important to secure a small timeframe at boot time, when
network is already configured, but pf(4) is not yet.
PR: kern/171622
Submitted by: Olivier Cochard-LabbИ <olivier cochard.me>
|
|
|
|
|
|
|
| |
Wrap two long lines.
Some minor spelling correction.
PR: usb/171721
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Remove cvs(1) references.
- Remove CVS* environment references.
- Add default entries for the default SVNROOT for the Ports
Collection, and Documentation Project.
- While here, update 'SGML-based documentation' to 'XML-based',
since the recent SGML->XML conversion.
- Update an example providing SVNROOT environment usage.
Reminded by: nwhitehorn
MFC After: 1 week
X-MFC-With: r240586, r240587
|
| |
|
|
|
|
|
|
| |
Document byteorder behavior in AF_INET[6] hooks in new section.
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
Describe SI_LWP as being generated by pthread_kill() because thr_kill() is
a private undocumented function.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
| |
PR: docs/171624
Submitted by: bdrewery
Approved by: gabor
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
reside, and move there ipfw(4) and pf(4).
o Move most modified parts of pf out of contrib.
Actual movements:
sys/contrib/pf/net/*.c -> sys/netpfil/pf/
sys/contrib/pf/net/*.h -> sys/net/
contrib/pf/pfctl/*.c -> sbin/pfctl
contrib/pf/pfctl/*.h -> sbin/pfctl
contrib/pf/pfctl/pfctl.8 -> sbin/pfctl
contrib/pf/pfctl/*.4 -> share/man/man4
contrib/pf/pfctl/*.5 -> share/man/man5
sys/netinet/ipfw -> sys/netpfil/ipfw
The arguable movement is pf/net/*.h -> sys/net. There are
future plans to refactor pf includes, so I decided not to
break things twice.
Not modified bits of pf left in contrib: authpf, ftp-proxy,
tftp-proxy, pflogd.
The ipfw(4) movement is planned to be merged to stable/9,
to make head and stable match.
Discussed with: bz, luigi
|
| |
|
|
|
|
|
|
| |
by rcng.
Reviewed by: wblock, dougb
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Regular LISTs have been implemented in such a way that the prev-pointer
does not point to the previous element, but to the next-pointer stored
in the previous element. This is done to simplify LIST_REMOVE(). This
macro can be implemented without knowing the address of the list head.
Unfortunately this makes it harder to implement LIST_PREV(), which is
why this macro was never here. Still, it is possible to implement this
macro. If the prev-pointer points to the list head, we return NULL.
Otherwise we simply subtract the offset of the prev-pointer within the
structure.
It's not as efficient as traversing forward of course, but in practice
it shouldn't be that bad. In almost all use cases, people will want to
compare the value returned by LIST_PREV() against NULL, so an optimizing
compiler will not emit code that does more branching than TAILQs.
While there, make the code a bit more readable by introducing
__member2struct(). This makes STAILQ_LAST() far more readable.
MFC after: 1 month
|
|
|
|
| |
Obtained from: r167342 commit message
|
| |
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
with the switch to subversion.
Approved by: gjb (man pages)
Approved by: cperciva (example files, implicit)
MFC after: 1 week
|