Anything you do in the NDIS layer would definitely slow down using
filter/intermediate structure. Even direct patching of the functions (
hooking ) is also somewhat time consuming, if you are just looking for
little information. All those pushing and popping
Args causes some headache here. Actually the idea is to have 3 methods in
parallel, in this particular case, 1) straight filter/intermediate driver,
2) direct patching 3) rerouting. Best performance is the method (3) —
-prokash
-----Original Message-----
From: Maxim S. Shatskih [mailto:xxxxx@storagecraft.com]
Sent: Tuesday, January 27, 2004 11:33 AM
To: Windows System Software Devs Interest List
Subject: Re: Re[2]: [ntdev] NtCreateSection() - relation between parent an d
child process
problem. If I remember correctly, font software such as the Adobe Type
Manager did that too.
In Win3.1, due to absense of documented ways of creating a font producer.
It’s not a question of being production software, it’s a question of
doing it
properly.
I agree. Hooking disk file IO is surely a bad design - use FS filter
instead. But, if there is no other, lesser dirty ways - hooking is OK IMHO.
OK, let’s says this - hooking is OK if it can be nearly mathematically
proven that the task is not solvable other ways. “Solvable” includes the
adequate performance, for sure.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@maxtor.com To
unsubscribe send a blank email to xxxxx@lists.osr.com