netdev - Re: loaded router, excessive getnstimeofday in oprofile

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <48B70E74.2000800@hp.com>
Date:	Thu, 28 Aug 2008 13:45:40 -0700
From:	Rick Jones <rick.jones2@...com>
To:	David Miller <davem@...emloft.net>
CC:	jmalicki@...acarta.com, andi@...stfloor.org, johnpol@....mipt.ru,
	dada1@...mosbay.com, denys@...p.net.lb, netdev@...r.kernel.org,
	linux-kernel@...r.kernel.org, juhlenko@...mai.com, sammy@...my.net
Subject: Re: loaded router, excessive getnstimeofday in oprofile

David Miller wrote:
> From: Rick Jones <rick.jones2@...com>
> Date: Thu, 28 Aug 2008 13:29:30 -0700
> 
> 
>>Has the request "hit the trading system" when it hits the NIC, or
>>when it hits the application executing the trade?  If the SEC calls
>>for when it hits the NIC, then none of what is done today is really
>>accurate/correct and one would need to start using NIC HW
>>timestamps, synchronized with the host and the other NICs in the
>>system no?
> 
> 
> The SEC isn't mandating anything here, stop framing it that way :-)

Must be my DC upbringing.  I figured that if the logic wasn't 100% 
concrete a US Federal Bureaucracy must be involved :)

> People simply won't trade with a firm if they find out that trades
> there are executed out of order.
> 
> They are simply trying to make things as fair as possible.

But that is the very crux of the question - exactly where is "in order" 
to be determined?  Is it supposed to be arrival time at the NIC HW, 
initial notice by the driver, or initial notice by the trading application?

Given that there are no guarantees that a packet arriving on NIC 1 and 
timestamped either by the NIC HW or the driver will actually hit the 
application before a packet arriving on NIC2, just how long are these 
financial services applications going to wait around before executing 
the trade carried in the packet arriving on NIC1?

rick jones
--
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