wi(4) - polling(4) changes / DEVICE_POLLING

[Luigi Rizzo]

if i remember well, the "wi" driver copies the packet from the card
to the mbuf using programmed I/O. Switching to polling will just
move the load under a different bucket (SYSTEM or IDLE instead
of INTR) but not change the situation radically, and i
doubt you will achieve significant performance improvements.

This said i cannot think of issues in making wi polling-aware,
as the polling code makes no assumptions on how the device works.

	cheers
	luigi

On Mon, Apr 21, 2003 at 01:05:52PM +0200, Dirk-Willem van Gulik wrote:
> 
> Is anyone actively working on making the polling(8) to the wi(4) driver ?
> 
> As in www.wirelessleiden.nl we're seeing very significant (>80%) INTR
> time spend when doing simple bridging from one wi(4) card to another on
> the lower end motherboards (P1, slow P2's).
> 
> And we have similarly seen that using DEVICE_POLLING on the sis(4) cards
> in the same device would instantly drop sis0<->sis1 INTR time resources to
> acceptible levels (and increase performance by almost a 2 fold).
> 
> Or are there any fundamental issues with making wi(4) polling(4) aware ?
> I.e. some specific firmware issues, etc ?
> 
> Thanks !
> 
> Dw
> 
> _______________________________________________
> freebsd-hackers at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org"