Re: [Announce] BKL shifting into drivers and filesystems - beware

• Next message: Meelis Roos: "RPC: garbage, exit EIO"
• Previous message: Andreas Schwab: "Re: SIGSEGV on fclose"
• In reply to: Jeff V. Merkey: "Re: [Announce] BKL shifting into drivers and filesystems - beware"
• Next in thread: Henning P. Schmiedehausen: "Re: [Announce] BKL shifting into drivers and filesystems - beware"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi,

> one in Linux. NT uses something called a forwarder chain in the DLL
> loader to handle this problem for dynanmically linked modules, though I
> agree that the way they do it is an absolute hack.

The main problem is that it doesn't handle accessing data elements at
all. In other words, you need to call a DLL function _for_everything_.
That's a serious performance killer.

In other words, it trades off performance against pseudo-compatibility.
(How many old NT drivers actually _do_ work with the new NT interfaces?
They may load, but then the whole thing crashes...)

-- 
Matthias Urlichs  |  noris network GmbH   |   smurf@noris.de  |  ICQ: 20193661
The quote was selected randomly. Really.       |        http://smurf.noris.de/
-- 
The best way to accelerate MS-Windows is at escape velocity.
-
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/

• Next message: Meelis Roos: "RPC: garbage, exit EIO"
• Previous message: Andreas Schwab: "Re: SIGSEGV on fclose"
• In reply to: Jeff V. Merkey: "Re: [Announce] BKL shifting into drivers and filesystems - beware"
• Next in thread: Henning P. Schmiedehausen: "Re: [Announce] BKL shifting into drivers and filesystems - beware"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sat Jul 15 2000 - 21:00:19 EST