Re: Probem with network performance 2.4.1

2001-02-20 Thread Mike Galbraith
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

Re: Probem with network performance 2.4.1

2001-02-20 Thread Richard B. Johnson
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

Probem with network performance 2.4.1

2001-02-20 Thread Richard B. Johnson
Given the following topography: | | | VXI RAM | |__| |--- |--|-| | Ethernet| | VXI bridge | | AMD PcNet32 | ||

Probem with network performance 2.4.1

2001-02-20 Thread Richard B. Johnson
Given the following topography: | | | VXI RAM | |__| |--- |--|-| | Ethernet| | VXI bridge | | AMD PcNet32 | ||

Re: Probem with network performance 2.4.1

2001-02-20 Thread Richard B. Johnson
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

Re: Probem with network performance 2.4.1

2001-02-20 Thread Mike Galbraith
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