Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1384235
| From | Cao jin <caoj.fnst@cn.fujitsu.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | [PATCH v2] hrtimers: doc cleanup |
| Date | 2016-04-21 15:40 +0200 |
| Message-ID | <rqmZS-1qh-45@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
It has: a tense correction(led->leads); a typo(unevitably->inevitably); Signed-off-by: Cao jin <caoj.fnst@cn.fujitsu.com> --- Documentation/timers/hrtimers.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Documentation/timers/hrtimers.txt b/Documentation/timers/hrtimers.txt index ce31f65..492f1af 100644 --- a/Documentation/timers/hrtimers.txt +++ b/Documentation/timers/hrtimers.txt @@ -28,9 +28,9 @@ several reasons why such integration is hard/impossible: - the unpredictable [O(N)] overhead of cascading leads to delays which necessitate a more complex handling of high resolution timers, which - in turn decreases robustness. Such a design still led to rather large + in turn decreases robustness. Such a design still leads to rather large timing inaccuracies. Cascading is a fundamental property of the timer - wheel concept, it cannot be 'designed out' without unevitably + wheel concept, it cannot be 'designed out' without inevitably degrading other portions of the timers.c code in an unacceptable way. - the implementation of the current posix-timer subsystem on top of -- 2.1.0
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
[PATCH v2] hrtimers: doc cleanup Cao jin <caoj.fnst@cn.fujitsu.com> - 2016-04-21 15:40 +0200
csiph-web