From: Benjamin LaHaise <[EMAIL PROTECTED]> Date: Fri, 23 Jun 2006 17:53:14 -0400
> The effect of doing all processing in user context creates issues > with delayed acks (due to context switching to other tasks in the system), The Linux TCP stack does this today. Full TCP input protocol processing is done in the user process context. What you are not understanding is that process scheduling helps TCP, it does not hinder it. If the system is loaded, we want the senders to pace themselves to the rate at which the kernel can schedule the abundance of receiver work it has. And this happens naturally when the TCP protocol input processing operates in process context. Your fear of cpu overcommit in interrupt handlers is also heavily flawed. Net channels do a socket demux, and a queue entail plus ring a doorbell if necessary, nothing more. - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
