From: Jan De Luyck <lkml@kcore.org>
To: Daniel Petrini <d.pensator@gmail.com>
Cc: linux-kernel@vger.kernel.org, Con Kolivas <kernel@kolivas.org>
Subject: Re: [PATCH] i386 No Idle HZ aka dynticks 051221
Date: Tue, 20 Dec 2005 21:46:12 +0100 [thread overview]
Message-ID: <200512202146.12737.lkml@kcore.org> (raw)
In-Reply-To: <9268368b0512201139v1836c920iaa6bdc11bd8f4e15@mail.gmail.com>
On Tuesday 20 December 2005 20:39, Daniel Petrini wrote:
> Hi Jan,
>
> On 12/20/05, Jan De Luyck <lkml@kcore.org> wrote:
> > One thing I'm curious about (and haven't tested yet): does this also work
> > with S3 suspend to ram? Last dynticks I tried had issues with that...
>
> I'm testing suspend to ram and it is working normally with dyn-ticks.
> What kind of problems are you facing?
I am facing none :) I just was facing (with an earlier dyntick patch, around
2.6.12.x) problems resuming with it. They seem to have been fixed
completely :)
In X i'm around 180HZ with everything up and running. Nice :) Very good work
everyone :)
Jan
--
Tu bi or not tu bi
DICK -- Começo de musica brega -- DICK vale o céu azul ...
next prev parent reply other threads:[~2005-12-20 19:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 16:10 [PATCH] i386 No Idle HZ aka dynticks 051221 Con Kolivas
2005-12-20 17:27 ` Jan De Luyck
2005-12-20 19:39 ` Daniel Petrini
2005-12-20 20:46 ` Jan De Luyck [this message]
2005-12-25 17:16 ` Theodore Ts'o
2005-12-26 2:55 ` Theodore Ts'o
2005-12-26 18:47 ` Matthew Garrett
2005-12-26 18:56 ` Theodore Ts'o
2005-12-26 20:03 ` Dominik Brodowski
2005-12-26 20:38 ` Pavel Machek
2005-12-26 22:52 ` Theodore Ts'o
2005-12-26 23:27 ` Pavel Machek
2005-12-27 14:03 ` Pavel Machek
2005-12-27 14:22 ` C4 strangeness [was Re: [PATCH] i386 No Idle HZ aka dynticks 051221] Pavel Machek
2005-12-27 15:33 ` C4 non-strangeness [was: " Dominik Brodowski
2005-12-27 16:13 ` Pavel Machek
2005-12-26 22:19 ` [PATCH] i386 No Idle HZ aka dynticks 051221 Dominik Brodowski
2005-12-27 0:33 ` Theodore Ts'o
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200512202146.12737.lkml@kcore.org \
--to=lkml@kcore.org \
--cc=d.pensator@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
/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