Source-Changes-HG archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

[src/trunk]: src/doc Note that kernels with NET_MPSAFE won't work with non-NE...



details:   https://anonhg.NetBSD.org/src/rev/5b20493551c2
branches:  trunk
changeset: 838513:5b20493551c2
user:      pgoyette <pgoyette%NetBSD.org@localhost>
date:      Mon Jan 21 02:28:25 2019 +0000

description:
Note that kernels with NET_MPSAFE won't work with non-NET_MPSAFE modules.

XXX The initial merge of the [pgoyette-compat] branch will NOT address
XXX this issue.

diffstat:

 doc/TODO.smpnet |  15 ++++++++++++++-
 1 files changed, 14 insertions(+), 1 deletions(-)

diffs (26 lines):

diff -r 79fe5d34fce1 -r 5b20493551c2 doc/TODO.smpnet
--- a/doc/TODO.smpnet   Mon Jan 21 01:02:50 2019 +0000
+++ b/doc/TODO.smpnet   Mon Jan 21 02:28:25 2019 +0000
@@ -1,4 +1,4 @@
-$NetBSD: TODO.smpnet,v 1.26 2018/12/12 07:07:30 maxv Exp $
+$NetBSD: TODO.smpnet,v 1.27 2019/01/21 02:28:25 pgoyette Exp $
 
 MP-safe components
 ==================
@@ -190,3 +190,16 @@
 the queue.  We should probably design and implement an alternative queuing
 mechanism that deals with multi-core systems at the first place, not making the
 existing ALTQ MP-safe because it's just annoying.
+
+Using kernel modules
+--------------------
+
+Please note that if you enable NET_MPSAFE in your kernel, and you use and
+loadable kernel modules (including compat_xx modules or individual network
+interface if_xxx device driver modules), you will need to build custom
+modules.  For each module you will need to add the following line to its
+Makefile:
+
+       CPPFLAGS+=      NET_MPSAFE
+
+Failure to do this may result in unpredictable behavior.



Home | Main Index | Thread Index | Old Index