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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 21 Nov 2007 10:15:30 -0500 From: jamal <hadi@...erus.ca> To: Ryousei Takano <takano-ryousei@...t.go.jp> Cc: netdev@...r.kernel.org, shemminger@...ux-foundation.org, t.kudoh@...t.go.jp Subject: Re: [RFC][PATCH 1/3] NET_SCHED: PSPacer qdisc module On Wed, 2007-21-11 at 19:18 +0900, Ryousei Takano wrote: > This patch includes the PSPacer (Precise Software Pacer) qdisc > module, which achieves precise transmission bandwidth control. > You can find more information at the project web page > (http://www.gridmpi.org/gridtcp.jsp). Good stuff. I have not read your paper - There are NICs out there (chelsio comes to mind) which claim to do pacing and have shown impressive numbers with TCP. Is your approach similar? Are there patents involved by some of these hardware vendors? (It would not be suprising if they exist). The advantage with NICs is they have very good control of the timing (clock granularity being extremely important in cases like this) - what were your measurements based on i.e what clock source did you use on Linux? Also, the idea of using a PAUSE frame to add gaps is interesting, but you should note that in linux a qdisc may be attached to any network device and this for example maybe a PPP device etc. What would you use for gaps in that case? I apologize if the answers are in your papers - i just glossed over. cheers, jamal - 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