From: Michael Harnois <mdharnois@home.com>
Date: 11 Feb 2000 00:03:57 -0600
(I was easily able to change vmnet to compile with the guide to the
tbusy changes, but I haven't yet been able to figure out what has
happened to start_bh_atomic or end_bh_atomic.)
It's a huge conceptual change, which is why I didn't try
to describe it in a HOWTO document.
Basically, people used to be able to use start_bh_atomic() and
basically turn off all network processing. This is no longer the case
with the fully threaded networking, you must use real SMP locking to
protect against whatever events the start_bh_atomic calls in vmware
are trying to synchronize with.
So if it is trying to read the state of some networking data
structure, you need to go into the networking and see how SMP
locking is done there to protect that data structure, etc.
This is not just a "replace this with this" type change, you
have to actually have to use your brain to fix it.
Later,
David S. Miller
davem@redhat.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:19 EST