lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 19 Jan 2007 11:27:02 -0500 From: Ayaz Abdulla <aabdulla@...dia.com> To: Jeff Garzik <jgarzik@...ox.com> CC: Manfred Spraul <manfred@...orfullife.com>, Andrew Morton <akpm@...l.org>, netdev@...r.kernel.org Subject: Re: [PATCH 10/12] forcedeth: tx max work Jeff Garzik wrote: > Ayaz Abdulla wrote: > > This patch adds a limit to how much tx work can be done in each > > iteration of tx processing. > > > > Signed-Off-By: Ayaz Abdulla <aabdulla@...dia.com> > > What about the "tail end" of the work, when the limit is reached? > > Remember that delaying the completion of TX's too long increases latency. > > It seems to me that this patch needs a timer or somesuch, to guarantee > that TX completions are not delayed too long in the worst case. Yes, you are right. There is a timer interrupt that fires in throughput mode every 10ms (in cpu mode it fires at approx every 130us). I can use that to clean out any uncompleted TXs. Let me know if 10ms is not too late for worst case tx completion. > > Jeff > > > - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists