Searched hist:48924 (Results 1 - 10 of 10) sorted by relevance

/freebsd-10.2-release/sys/i386/include/
H A Dsmp.hdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)
/freebsd-10.2-release/sys/sys/
H A Dsmp.hdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)
/freebsd-10.2-release/sys/amd64/include/
H A Dsmp.hdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)
/freebsd-10.2-release/sys/i386/i386/
H A Dapic_vector.sdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)
H A Dmp_machdep.cdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)
/freebsd-10.2-release/sys/amd64/amd64/
H A Dapic_vector.Sdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)
H A Dmp_machdep.cdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)
/freebsd-10.2-release/sys/kern/
H A Dsubr_smp.cdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)
/freebsd-10.2-release/sys/x86/include/
H A Dmptable.hdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)
/freebsd-10.2-release/sys/x86/x86/
H A Dmptable.cdiff 48924 Tue Jul 20 06:52:35 MDT 1999 msmith Implement an all-CPU shootdown-style rendezvous facility. This allows
the caller to specify a function to be guarded between an entry and exit
barrier, as well as pre- and post-barrier functions.

The primary use for this function is synchronised update of per-cpu private
data. The implementation is almost (but not quite) MI; with a better
mechanism for masking per-CPU interrupts it could probably be hoisted.

Reviewed by: peter (partially)

Completed in 480 milliseconds