From: Anton Vorontsov <anton.vorontsov@linaro.org>
To: leonid.moiseichuk@nokia.com
Cc: penberg@kernel.org, linux-kernel@vger.kernel.org, rientjes@google.com
Subject: Re: [PATCH] vmevent: Use 'struct vmevent_attr' for vmevent_fd() ABI
Date: Wed, 7 Mar 2012 17:22:28 +0400 [thread overview]
Message-ID: <20120307132228.GA30159@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <84FF21A720B0874AA94B46D76DB9826904581EF7@008-AM1MPN1-003.mgdnok.nokia.com>
On Wed, Mar 07, 2012 at 07:53:37AM +0000, leonid.moiseichuk@nokia.com wrote:
> > -----Original Message-----
> > From: ext Anton Vorontsov [mailto:anton.vorontsov@linaro.org]
> > Sent: 07 March, 2012 01:00
> > To: Pekka Enberg
> > Cc: linux-kernel@vger.kernel.org; Moiseichuk Leonid (Nokia-MP/Espoo);
> ...
> > Sorry for hijacking this thread, but speaking of big changes. Are there any
> > plans or ideas to add other methods of sampling, i.e. something not timer-
> > based?
> ...
> > Though, current vmevent seems not so lightweigh in sense of battery usage
> > and accuracy (i.e. how quick we're able to detect the crossed threshold). To
> > get better accuracy we would need to run timer at higher frequencies, but
> > then we would waste more battery.
>
> One of patch I sent was about switching to deferred timer. This API should not be 100% accurate first, and using deferred
> timers will allow to sleep properly when system has no activity. I hope Pekka will accept the next patch as well.
Nice idea!
Thanks,
--
Anton Vorontsov
Email: cbouatmailru@gmail.com
next prev parent reply other threads:[~2012-03-07 13:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 20:51 [PATCH] vmevent: Use 'struct vmevent_attr' for vmevent_fd() ABI Pekka Enberg
2012-03-06 22:59 ` Anton Vorontsov
2012-03-07 7:53 ` leonid.moiseichuk
2012-03-07 10:03 ` Pekka Enberg
2012-03-07 13:22 ` Anton Vorontsov [this message]
2012-03-07 10:08 ` Pekka Enberg
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=20120307132228.GA30159@oksana.dev.rtsoft.ru \
--to=anton.vorontsov@linaro.org \
--cc=leonid.moiseichuk@nokia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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