#
331722 |
|
29-Mar-2018 |
eadler |
Revert r330897:
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)
|
#
330897 |
|
14-Mar-2018 |
eadler |
Partial merge of the SPDX changes
These changes are incomplete but are making it difficult to determine what other changes can/should be merged.
No objections from: pfg
|
#
302408 |
|
07-Jul-2016 |
gjb |
Copy head@r302406 to stable/11 as part of the 11.0-RELEASE cycle. Prune svn:mergeinfo from the new branch, as nothing has been merged here.
Additional commits post-branch will follow.
Approved by: re (implicit) Sponsored by: The FreeBSD Foundation |
#
199615 |
|
20-Nov-2009 |
jkim |
General style cleanup, no functional change.
|
#
199603 |
|
20-Nov-2009 |
jkim |
- Allocate scratch memory on stack instead of pre-allocating it with the filter as we do from bpf_filter()[1]. - Revert experimental use of contigmalloc(9)/contigfree(9). It has no performance benefit over malloc(9)/free(9)[2].
Requested by: rwatson[1] Pointed out by: rwatson, jhb, alc[2]
|
#
199498 |
|
18-Nov-2009 |
jkim |
- Change internal function bpf_jit_compile() to return allocated size of the generated binary and remove page size limitation for userland. - Use contigmalloc(9)/contigfree(9) instead of malloc(9)/free(9) to make sure the generated binary aligns properly and make it physically contiguous.
|
#
199492 |
|
18-Nov-2009 |
jkim |
- Make BPF JIT compiler working again in userland. We are limiting size of generated native binary to page size for now. - Update copyright date and fix some style nits.
|
#
182376 |
|
28-Aug-2008 |
jkim |
Initialize scratch memory for JIT-compiled filter when it is allocated. Previously it may have contained unnecessary (even sensitive) data from the previous allocation. As a (good) side effect, scratch memory may be used to store the previous filter state(s) safely because it is allocated and freed with filter itself. However, use it carefully because bpf_filter(9) does not have this behavior.
MFC after: 3 days
|
#
182220 |
|
26-Aug-2008 |
jkim |
Move empty filter handling to MI source.
MFC after: 3 days
|
#
182173 |
|
25-Aug-2008 |
jkim |
Fix a typo in copyrights.
|
#
182172 |
|
25-Aug-2008 |
jkim |
Embed scratch memory in the filter structure.
MFC after: 3 days
|
#
181846 |
|
18-Aug-2008 |
jkim |
- Make these files compilable on user land. - Update copyrights and fix style(9).
|
#
153213 |
|
07-Dec-2005 |
jkim |
Add BPF Just-In-Time compiler support for ng_bpf(4).
The sysctl is changed from net.bpf.jitter.enable to net.bpf_jitter.enable and this controls both bpf(4) and ng_bpf(4) now.
|
#
153157 |
|
06-Dec-2005 |
jkim |
s/M_WAITOK/M_NOWAIT/ while mutex is held.
Pointed out by: csjp
|
#
153151 |
|
06-Dec-2005 |
jkim |
Add experimental BPF Just-In-Time compiler for amd64 and i386.
Use the following kernel configuration option to enable:
options BPF_JITTER
If you want to use bpf_filter() instead (e. g., debugging), do:
sysctl net.bpf.jitter.enable=0
to turn it off.
Currently BIOCSETWF and bpf_mtap2() are unsupported, and bpf_mtap() is partially supported because 1) no need, 2) avoid expensive m_copydata(9).
Obtained from: WinPcap 3.1 (for i386)
|