Don
Fri Aug 04 07:47:12 CDT 2006
No call table hacking was minor hacking compared to what you are looking at.
It might be easier to look at writing your own kernel.
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
http://www.windrvr.com
Remove StopSpam from the email to reply
<grishka@gmail.com> wrote in message
news:1154694933.880099.60480@i42g2000cwa.googlegroups.com...
>I agree with you about "extreme hacking", but remember that brilliant
> things, such as RegMon by SysInternals wouldn't be possible had its
> authors stick to "standard" methods only and avoid patching system
> call pointer table.
>
> Don Burn wrote:
>> Then so is reasonable performance, anything you try will be an extreme
>> hack
>> that will likely not be stable under stress. Since you have already said
>> the system is going to be stressed with large inputs since you care about
>> performance, you are in a lose or lose situation.
>>
>> Note, trying to hack around with the MDL is a dead end, there is more to
>> the
>> memory manager than that.
>>
>>
>> --
>> Don Burn (MVP, Windows DDK)
>> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>>
http://www.windrvr.com
>> Remove StopSpam from the email to reply
>>
>>
>> <grishka@gmail.com> wrote in message
>> news:1154694149.595192.268790@m73g2000cwd.googlegroups.com...
>> > If that was a good news, I wouldn't ask my question here :)
>> > I do have quite a bit of experience in kernel mode and I'm aware of the
>> > "right" and "wrong" ways of doing things. However, that's the task I
>> > have and changing the other driver is definitely out of question.
>> >
>> > Don Burn wrote:
>> >> Sorry but the opaque driver is bad news. If you are going to get
>> >> performance you need to fix that driver, any other schema by you is
>> >> going
>> >> to
>> >> result in a copy sooner or later.
>> >>
>> >>
>> >> --
>> >> Don Burn (MVP, Windows DDK)
>> >> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>> >>
http://www.windrvr.com
>> >> Remove StopSpam from the email to reply
>> >>
>> >>
>> >>
>> >> <grishka@gmail.com> wrote in message
>> >> news:1154693345.963482.31520@p79g2000cwp.googlegroups.com...
>> >> >1 GB/s. The data is delivered by a PCI device DMA into kernel buffers
>> >> > allocated by another (opaque) driver. Copying the data into
>> >> > IOCTL-supplied buffer utilizes CPU above the acceptable limit (about
>> >> > 5%
>> >> > CPU usage on the most powerful machine I have, 20-30% on a typical
>> >> > one). Once more, I can not supply my buffers for delivery. I can
>> >> > just
>> >> > have pointers to those owned by the other driver.
>> >> >
>> >> > Maxim S. Shatskih wrote:
>> >> >> > Copying this amount of data eats up an unacceptable amount of
>> >> >> > CPU.
>> >> >>
>> >> >> How many MB/s? What is your exact task?
>> >> >>
>> >> >> --
>> >> >> Maxim Shatskih, Windows DDK MVP
>> >> >> StorageCraft Corporation
>> >> >> maxim@storagecraft.com
>> >> >>
http://www.storagecraft.com
>> >> >
>> >
>