Date: Sun, 10 Sep 2000 18:14:03 -0600 From: "Jeff V. Merkey" <[EMAIL PROTECTED]> Linus' apparently did not understand this, or he would have immediately realized that double locking was always generating a second non-cacheable memory reference for every lock being taken and released. Jeff, after working together with Linus for 6 or so years myself, I would make a large wager that Linus understands these issues much better than even you. But then again, as previously stated, I don't take you very seriously, but I fear that there are a few on this list who still do. Later, David S. Miller [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Availability of kdb Gary Lawrence Murphy
- Re: Availability of kdb Martin Dalecki
- Re: Availability of kdb Jeff V. Merkey
- Re: Availability of kdb J. Dow
- Re: Availability of kdb Linus Torvalds
- Re: Availability of kdb Nathan Paul Simons
- Re: Availability of kdb Bob Taylor
- Re: Availability of kdb Jeff V. Merkey
- Re: Availability of kdb Alexander Viro
- Re: Availability of kdb Jeff V. Merkey
- Re: Availability of kdb David S. Miller
- Re: Availability of kdb Jeff V. Merkey
- Re: Availability of kdb Jeff V. Merkey
- Re: Availability of kdb Jamie Lokier
- Re: Availability of kdb Jeff V. Merkey
- Re: Availability of kdb Jamie Lokier
- Re: Availability of kdb Jeff V. Merkey
- Re: Availability of kdb Jamie Lokier
- Re: Availability of kdb Lars Marowsky-Bree
- Re: Availability of kdb Jamie Lokier
- Re: Availability of kdb Jeff V. Merkey