I’m not going to do it in a way that allows arbitrary drivers to make
themselves the highest priority. I don’t want to go into more detail
here, since talking about future products is legally tricky.
Your point is a good one, though. Designers of devices have an economic
incentive to make their device perform better than a competitor’s, even
at the expense of overall system performance. I’d like to think that
large companies wouldn’t buy stuff that’s designed so poorly that, in
order to function competitively, the driver has to hammer system
performance. (Consumers never have the means to make such
distinctions.) But in reality, it happens. So we have to find a way to
sort it all out and keep the machines running.
Jake Oshins
Windows Kernel Group
This posting is provided “AS IS” with no warranties, and confers no
rights.
-----Original Message-----
Subject: RE: Device Interrupt Priority
From: “Dan Partelly”
Date: Thu, 5 Sep 2002 20:13:34 +0300
X-Message-Number: 32
Jake,
>> I’m currently in the process of changing this for a possible future
NT
release.
Wouldnt then everybody , whatever they need it or not, try to grasp
highest
interrupt priority, just because they can ? Wont it open a can full of
worms
?
Dan
----- Original Message -----
From: “Jake Oshins”
To: “NT Developers Interest List”
Sent: Thursday, September 05, 2002 7:59 PM
Subject: [ntdev] RE: Device Interrupt Priority
I’m sorry to tell you that there aren’t any legal things that you can do
to influence a device’s IRQL. I’m currently in the process of changing
this for a possible future NT release. But that’s not going to be
helpful to you at the moment.
Jake Oshins
Windows Kernel Group
This posting is provided “AS IS” with no warranties, and confers no
rights.
>> make their device perform better than a competitor’s,
Or they simply cant read a specification and obey it. I love ppl who write
filters on the storage stack and they aint even able to conform basic PNP
rules and even more sad, corectly moddig the registry filter entries. I want
as well to beleive this will change
one day.
As for KeIpiGenericCall Im glad you guys finally decided to expose it.
Ciao, Dan
----- Original Message -----
From: “Jake Oshins”
To: “NT Developers Interest List”
Sent: Friday, September 06, 2002 8:17 PM
Subject: [ntdev] RE: Device Interrupt Priority - self determination of
priority
I’m not going to do it in a way that allows arbitrary drivers to make
themselves the highest priority. I don’t want to go into more detail
here, since talking about future products is legally tricky.
Your point is a good one, though. Designers of devices have an economic
incentive to make their device perform better than a competitor’s, even
at the expense of overall system performance. I’d like to think that
large companies wouldn’t buy stuff that’s designed so poorly that, in
order to function competitively, the driver has to hammer system
performance. (Consumers never have the means to make such
distinctions.) But in reality, it happens. So we have to find a way to
sort it all out and keep the machines running.
Jake Oshins
Windows Kernel Group
This posting is provided “AS IS” with no warranties, and confers no
rights.
-----Original Message-----
Subject: RE: Device Interrupt Priority
From: “Dan Partelly”
Date: Thu, 5 Sep 2002 20:13:34 +0300
X-Message-Number: 32
Jake,
>> I’m currently in the process of changing this for a possible future
NT
release.
Wouldnt then everybody , whatever they need it or not, try to grasp
highest
interrupt priority, just because they can ? Wont it open a can full of
worms
?
Dan
----- Original Message -----
From: “Jake Oshins”
To: “NT Developers Interest List”
Sent: Thursday, September 05, 2002 7:59 PM
Subject: [ntdev] RE: Device Interrupt Priority
I’m sorry to tell you that there aren’t any legal things that you can do
to influence a device’s IRQL. I’m currently in the process of changing
this for a possible future NT release. But that’s not going to be
helpful to you at the moment.
Jake Oshins
Windows Kernel Group
This posting is provided “AS IS” with no warranties, and confers no
rights.
—
You are currently subscribed to ntdev as: xxxxx@rdsor.ro
To unsubscribe send a blank email to %%email.unsub%%
>performance. (Consumers never have the means to make such
distinctions.) But in reality, it happens. So we have to find a way
to
Nobody except MS seem to be able of putting end to this. Maybe you
would refuse to digitally sign the drivers which try to squeeze
performance at the cost of stability and reliability?
Max