if_flags is neither int nor short. It's unsigned short.

branches: 1.4.2;
s/static inline/static __inline/g for consistency.

branches: 1.3.36;
split device_t/softc for all remaining drivers.
replace "struct device *" with "device_t".
use device_xname(), device_unit(), etc.

branches: 1.2.4; 1.2.14;
MI code must #include <sys/bus.h>, not <machine/bus.h>.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

s/collissions/collisions/

s/static inline/static __inline/g for consistency.

branches: 1.2.36;
Make cxgb at least compilable. Fix _rt_key usage.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.14; 1.1.24;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

Fix various typos, mainly triple letters.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

Fix CVS Id usage

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.66;
Reorganizing all Chelsio 10 gig files into separate directory.

More on PR 41200: headers that declare ioctls should include sys/ioccom.h.
This covers (I think) all the MI headers outside of external/ (and dist/).

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.24; 1.1.42;
Reorganizing all Chelsio 10 gig files into separate directory.

s/partilar/particular/ in comment.

branches: 1.2.40;
s/static inline/static __inline/g for consistency.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.64;
Reorganizing all Chelsio 10 gig files into separate directory.

Replace M_ALIGN and MH_ALIGN by m_align.

branches: 1.4.14; 1.4.16;
There are two memory leaks here, found by mootja; just add some XXXs.

branches: 1.3.6; 1.3.10;
kill sprintf

branches: 1.2.2;
Make cxgb at least compilable. Fix _rt_key usage.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.14; 1.1.24;
Reorganizing all Chelsio 10 gig files into separate directory.

s/static inline/static __inline/g for consistency.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.64;
Reorganizing all Chelsio 10 gig files into separate directory.

MI code must #include <sys/bus.h>, not <machine/bus.h>.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8;
Reorganizing all Chelsio 10 gig files into separate directory.

Merge thorpej-cfargs2.

branches: 1.9.8;
Merge thorpej-cfargs branch:

Simplify and make extensible the config_search() / config_found() /
config_attach() interfaces: rather than having different variants for
which arguments you want pass along, just have a single call that
takes a variadic list of tag-value arguments.

Adjust all call sites:
- Simplify wherever possible; don't pass along arguments that aren't
actually needed.
- Don't be explicit about what interface attribute is attaching if
the device only has one. (More simplification.)
- Add a config_probe() function to be used in indirect configuiration
situations, making is visibly easier to see when indirect config is
in play, and allowing for future change in semantics. (As of now,
this is just a wrapper around config_match(), but that is an
implementation detail.)

Remove unnecessary or redundant interface attributes where they're not
needed.

There are currently 5 "cfargs" defined:
- CFARG_SUBMATCH (submatch function for direct config)
- CFARG_SEARCH (search function for indirect config)
- CFARG_IATTR (interface attribte)
- CFARG_LOCATORS (locators array)
- CFARG_DEVHANDLE (devhandle_t - wraps OFW, ACPI, etc. handles)

...and a sentinel value CFARG_EOL.

Add some extra sanity checking to ensure that interface attributes
aren't ambiguous.

Use CFARG_DEVHANDLE in MI FDT, OFW, and ACPI code, and macppc and shark
ports to associate those device handles with device_t instance. This
will trickle trough to more places over time (need back-end for pre-OFW
Sun OBP; any others?).

branches: 1.8.8;
Use ifmedia_fini().

branches: 1.7.6;
use pci_intr_establish_xname()

XXX due to 2008-01-17 '10 gigabit Chelsio cards now compile and work, although
XXX not very well yet' commit this looks like having worked in past, but since
XXX ~2010 received only mechanical updates, and currently it's unreferenced
XXX and uncompilable - does it make sense to keep the driver around?

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.5.2;
Implement the BPF direction filter (BIOC[GS]DIRECTION). It provides backward
compatibility with BIOC[GS]SEESENT ioctl. The userland interface is the same
as FreeBSD.

This change also fixes a bug that the direction is misunderstand on some
environment by passing the direction to bpf_mtap*() instead of checking
m->m_pkthdr.rcvif.

branches: 1.4.36;
Make cxgb at least compilable. Fix _rt_key usage.

split device_t/softc for all remaining drivers.
replace "struct device *" with "device_t".
use device_xname(), device_unit(), etc.

branches: 1.2.4; 1.2.14;
MI code must #include <sys/bus.h>, not <machine/bus.h>.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

Typos.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

s/static inline/static __inline/g for consistency.

branches: 1.2.14;
MFREE -> m_free

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.24; 1.1.42; 1.1.46;
Reorganizing all Chelsio 10 gig files into separate directory.

s/propely/properly/

s/suport/support/

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.4.18; 1.4.20;
comment out code that was never used, but probably intended to be used.

branches: 1.3.4;
kill sprintf

branches: 1.2.4; 1.2.14; 1.2.18;
MI code must #include <sys/bus.h>, not <machine/bus.h>.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8;
Reorganizing all Chelsio 10 gig files into separate directory.

s/static inline/static __inline/g for consistency.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.64;
Reorganizing all Chelsio 10 gig files into separate directory.

MI code must #include <sys/bus.h>, not <machine/bus.h>.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8;
Reorganizing all Chelsio 10 gig files into separate directory.

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.6.2;
s/static inline/static __inline/g for consistency.

branches: 1.5.16;
Use M_GETCTX and M_SETCTX

No functional change.

branches: 1.4.6;
Mechanically replace simplelock with kmutex_t.

branches: 1.3.2;
Make cxgb at least compilable. Fix _rt_key usage.

branches: 1.2.4; 1.2.14;
MI code must #include <sys/bus.h>, not <machine/bus.h>.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

fix few typos in comments.

branches: 1.7.36;
Replace M_ALIGN and MH_ALIGN by m_align.

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.5.2; 1.5.4;
VLAN ID uses pkthdr instead of mtag now. Contributed by s-yamaguchi@IIJ.

I just commit by proxy. Reviewed by joerg@n.o and christos@n.o, thanks.
See http://mail-index.netbsd.org/tech-net/2017/09/26/msg006459.html

XXX need pullup to -8 branch

branches: 1.4.10;
Introduce m_set_rcvif and m_reset_rcvif

The API is used to set (or reset) a received interface of a mbuf.
They are counterpart of m_get_rcvif, which will come in another
commit, hide internal of rcvif operation, and reduce the diff of
the upcoming change.

No functional change.

Introduce softint-based if_input

This change intends to run the whole network stack in softint context
(or normal LWP), not hardware interrupt context. Note that the work is
still incomplete by this change; to that end, we also have to softint-ify
if_link_state_change (and bpf) which can still run in hardware interrupt.

This change softint-ifies at ifp->if_input that is called from
each device driver (and ieee80211_input) to ensure Layer 2 runs
in softint (e.g., ether_input and bridge_input). To this end,
we provide a framework (called percpuq) that utlizes softint(9)
and percpu ifqueues. With this patch, rxintr of most drivers just
queues received packets and schedules a softint, and the softint
dequeues packets and does rest packet processing.

To minimize changes to each driver, percpuq is allocated in struct
ifnet for now and that is initialized by default (in if_attach).
We probably have to move percpuq to softc of each driver, but it's
future work. At this point, only wm(4) has percpuq in its softc
as a reference implementation.

Additional information including performance numbers can be found
in the thread at tech-kern@ and tech-net@:
http://mail-index.netbsd.org/tech-kern/2016/01/14/msg019997.html

Acknowledgment: riastradh@ greatly helped this work.
Thank you very much!

branches: 1.2.14; 1.2.32;
MI code must #include <sys/bus.h>, not <machine/bus.h>.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.8;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

s/Perfoms/Performs/ in comment.

branches: 1.8.2;
s/separare/separate/ and s/separete/separate/ in comments.

s/occured/occurred/ in comments, log messages and man pages.

s/endianess/endianness/

fix various typos in comments and log messages.

s/occurence/occurrence/

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.2.2; 1.2.4;
Typos.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

s/static inline/static __inline/g for consistency.

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.64;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

branches: 1.1.2; 1.1.4; 1.1.6;
Reorganizing all Chelsio 10 gig files into separate directory.

fix various typos in documentation, comments and sysctl device description.
mainly aion -> ation and inlude -> include.

Rename min/max -> uimin/uimax for better honesty.

These functions are defined on unsigned int. The generic name
min/max should not silently truncate to 32 bits on 64-bit systems.
This is purely a name change -- no functional change intended.

HOWEVER! Some subsystems have

#define min(a, b) ((a) < (b) ? (a) : (b))
#define max(a, b) ((a) > (b) ? (a) : (b))

even though our standard name for that is MIN/MAX. Although these
may invite multiple evaluation bugs, these do _not_ cause integer
truncation.

To avoid `fixing' these cases, I first changed the name in libkern,
and then compile-tested every file where min/max occurred in order to
confirm that it failed -- and thus confirm that nothing shadowed
min/max -- before changing it.

I have left a handful of bootloaders that are too annoying to
compile-test, and some dead code:

cobalt ews4800mips hp300 hppa ia64 luna68k vax
acorn32/if_ie.c (not included in any kernels)
macppc/if_gm.c (superseded by gem(4))

It should be easy to fix the fallout once identified -- this way of
doing things fails safe, and the goal here, after all, is to _avoid_
silent integer truncations, not introduce them.

Maybe one day we can reintroduce min/max as type-generic things that
never silently truncate. But we should avoid doing that for a while,
so that existing code has a chance to be detected by the compiler for
conversion to uimin/uimax without changing the semantics until we can
properly audit it all. (Who knows, maybe in some cases integer
truncation is actually intended!)

branches: 1.1.2; 1.1.4; 1.1.6; 1.1.64; 1.1.66;
Reorganizing all Chelsio 10 gig files into separate directory.