<br><font size=2><tt>openib-general-bounces@openib.org wrote on 05/09/2006
11:57:01 AM:<br>
<br>
> On 09.05.2006, at 18:49, Michael S. Tsirkin wrote:<br>
> <br>
> >> The trivial way to do it would be to use the same idea as
the current<br>
> >> ehca driver: just create a thread for receive CQ events and
a thread<br>
> >> for send CQ events, and defer CQ polling into those two threads.<br>
> ><br>
> > For RX, isn't this basically what NAPI is doing?<br>
> > Only NAPI seems better, avoiding interrupts completely and avoiding
<br>
> > latency hit<br>
> > by only getting triggered on high load ...<br>
> <br>
> Does NAPI schedules CQ callbacks to different CPUs or stays the callback<br>
> (handling of data, etc.) on the same CPU where the interrupt came
in?<br>
> <br>
> Regards,<br>
> Heiko<br>
</tt></font>
<br><font size=2 face="sans-serif">My understanding is NAPI handle interrutps
CQ callbacks on the same CPU. </font>
<br><font size=2 face="sans-serif">But you could implement NAPI differently,
then it doesn't follow the native NAPI </font>
<br><font size=2 face="sans-serif">implementation.</font>
<br><font size=2 face="sans-serif"><br>
Thanks<br>
Shirley Ma<br>
IBM Linux Technology Center<br>
15300 SW Koll Parkway<br>
Beaverton, OR 97006-6063<br>
Phone(Fax): (503) 578-7638</font>