From: Matthew Ford <ford@isoc.org>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] low latency workshop
Date: Thu, 20 Jun 2013 09:58:15 +0100 [thread overview]
Message-ID: <81F8FFF3-0AB7-490C-90C8-DD9957761E0F@isoc.org> (raw)
In-Reply-To: <CAA93jw5QCEbCAxvb3DG=H6TJFU6P5SSicKQuTkKo4Fi0uLvWWA@mail.gmail.com>
On 19 Jun 2013, at 22:27, Dave Taht <dave.taht@gmail.com> wrote:
> I was trying to find the isoc/rite low latency workshop info
http://www.internetsociety.org/latency2013
> via
> google today and stumbled across a competing event in london and a
> whole website dedicated to the latency issues in the trading industry.
Interesting, thanks for the pointer. I wouldn't describe it as competing though - seems pretty focussed on the high-frequency trading application, although there is obviously overlap.
Mat
>
> This talk
>
> http://low-latency.com/audio/london-low-latency-summit-2013-workshop-low-latency-application-engineering
>
> had slide 18 showing the enormous improvement in from-userspace
> timestamp fetching behavior in linux - from 637ns for CLOCK_REALTIME
> in 2.6.27, to 35ns in linux 3.5.4...
>
> Based on some old scars I was leery of using timestamping in userspace
> for some tasks. No longer.
>
> There are also some boards that look useful for analyzing hard
> networking stuff in detail mentioned.
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
prev parent reply other threads:[~2013-06-20 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 21:27 Dave Taht
2013-06-20 8:58 ` Matthew Ford [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81F8FFF3-0AB7-490C-90C8-DD9957761E0F@isoc.org \
--to=ford@isoc.org \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox