[lkml]   [2008]   [Aug]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: loaded router, excessive getnstimeofday in oprofile
> The issue is the ordering of processing the requests.
> So if request A arrived on interface 1 before request B arrived on
> interface 2, the trade described in A should be performed before the
> one in B.
> This is not "arcance" as you seem to suppose it might be, but rather
> pretty clear fair handling or requests sent between trading desks.

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 way things are today, there really isn't much guarantee that hitting
NIC 1 before NIC 2 will result in a driver-generated timestamp for the
NIC 1 packet which is before the driver-generated timestamp for the NIC
2 packet. It will be luck of the interrupt coalescing interaction with
other traffic on the NIC and/or polling out of NAPI right?

rick jones

 \ /
  Last update: 2008-08-28 22:33    [W:0.107 / U:20.020 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site