Date: Thu, 3 Jan 2013 09:41:26 +0100 From: Luigi Rizzo <rizzo@iet.unipi.it> To: Kevin Oberman <kob6558@gmail.com> Cc: Davide Italiano <davide@freebsd.org>, Ian Lepore <freebsd@damnhippie.dyndns.org>, Adrian Chadd <adrian@freebsd.org>, Alexander Motin <mav@freebsd.org>, freebsd-arch@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, Marius Strobl <marius@alchemy.franken.de> Subject: Re: [RFC/RFT] calloutng Message-ID: <20130103084126.GC54360@onelab2.iet.unipi.it> In-Reply-To: <CAN6yY1vRJN8EpKpYARfkShRzmPfC4VEw33O1mfppZ%2BD%2B8iebgQ@mail.gmail.com> References: <20121231061735.GA5866@onelab2.iet.unipi.it> <50E16637.9070501@FreeBSD.org> <20130102105730.GA42542@onelab2.iet.unipi.it> <50E418EA.7030801@FreeBSD.org> <20130102122743.GA43241@onelab2.iet.unipi.it> <CAO4K=PUHAH=UNzMde0V2TwkN5vj3gw9hHj5yCQxDvdUn%2Buqv7w@mail.gmail.com> <1357135374.54953.150.camel@revolution.hippie.lan> <CAJ-Vmo=mmm5zhwHyzKeg1VEL8hSz6_LxJAaLh74ArHF3_9KWaQ@mail.gmail.com> <50E4AF4C.2070902@FreeBSD.org> <CAN6yY1vRJN8EpKpYARfkShRzmPfC4VEw33O1mfppZ%2BD%2B8iebgQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 02, 2013 at 09:52:37PM -0800, Kevin Oberman wrote: > On Wed, Jan 2, 2013 at 2:06 PM, Alexander Motin <mav@freebsd.org> wrote: > > On 02.01.2013 18:08, Adrian Chadd wrote: > >> > >> .. I'm pretty damned sure we're going to need to enforce a "never > >> earlier than X" latency. > > > > > > Do you mean here that we should never wake up before specified time (just as > > specified by the most of existing APIs), or that we should not allow sleep > > shorter then some value to avoid DoS? At least on x86 nanosleep(0) doesn't > > allow to block the system. Also there is already present mechanism for > > specifying minimum timer programming interval in eventtimers(9) KPI. > > I can see serious performance issues with some hardware (wireless > comes to mind) if things happen too quickly. Intuition is that it > could also play hob with VMs. > > I believe that the proper way is to wake between T_X and T_X + D. > This assumes that D is max_wake_delay, not deviation, which leaves us > at the original of (T_X) =< event_time =< (T_X + D). i think "max delay" was the intended meaning of the D parameter. We picked bad names (tolerance, deviation,...) for it. cheers luigi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130103084126.GC54360>