| 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
| ||
|
Message-Id: <20100501010735.dfe097bc.billfink@mindspring.com> Date: Sat, 1 May 2010 01:07:35 -0400 From: Bill Fink <billfink@...dspring.com> To: David Miller <davem@...emloft.net> Cc: therbert@...gle.com, netdev@...r.kernel.org Subject: Re: [PATCH] tcp: SO_TIMESTAMP implementation for TCP On Fri, 30 Apr 2010, David Miller wrote: > From: Tom Herbert <therbert@...gle.com> > Date: Fri, 30 Apr 2010 00:58:32 -0700 > > >> All these new checks and branches for a feature of questionable value. > > > >> If you can modify you apps to grab this information you can also probe > >> for the information using external probing tools. > >> > > I don't see an nice way to do that, we're profiling a significant > > percentage of millions of connections over thousands of paths as part > > of standard operations while incurring negligible overhead. The app > > can can easily timestamp its operations, but without some mechanism > > for getting timestamps out of a TCP connection, the networking portion > > of servicing requests is pretty much a black box in that. > > If other people have an opinion about this, now would be the time > to speak up. :-) Not being a kernel hacker, I will naively ask if the kernel tracing facility could somehow be used to provide the desired info (or could be modified to provide it). -Bill -- 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