On Tue, 20 Feb 2001, Richard B. Johnson wrote:
> There is nothing in either the VXI/Bus driver or the the Ethernet
> driver that gives up the CPU, i.e., nobody calls schedule() in any
> (known) path.
Check out IKD. Ktrace is wonderful for making such unknowns visible.
-Mike
-
To
On Tue, 20 Feb 2001, Mike Galbraith wrote:
> On Tue, 20 Feb 2001, Richard B. Johnson wrote:
>
> > There is nothing in either the VXI/Bus driver or the the Ethernet
> > driver that gives up the CPU, i.e., nobody calls schedule() in any
> > (known) path.
>
> Check out IKD. Ktrace is wonderful
Given the following topography:
| |
| VXI RAM |
|__|
|---
|--|-| | Ethernet|
| VXI bridge | | AMD PcNet32 |
||
Given the following topography:
| |
| VXI RAM |
|__|
|---
|--|-| | Ethernet|
| VXI bridge | | AMD PcNet32 |
||
On Tue, 20 Feb 2001, Mike Galbraith wrote:
On Tue, 20 Feb 2001, Richard B. Johnson wrote:
There is nothing in either the VXI/Bus driver or the the Ethernet
driver that gives up the CPU, i.e., nobody calls schedule() in any
(known) path.
Check out IKD. Ktrace is wonderful for making
On Tue, 20 Feb 2001, Richard B. Johnson wrote:
There is nothing in either the VXI/Bus driver or the the Ethernet
driver that gives up the CPU, i.e., nobody calls schedule() in any
(known) path.
Check out IKD. Ktrace is wonderful for making such unknowns visible.
-Mike
-
To
6 matches
Mail list logo