public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Grothoff <christian@grothoff.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Alejandra Morales <alejandra.morales@tum.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Cryogenic: Enabling Power-Aware Applications on Linux
Date: Sat, 12 Apr 2014 01:51:03 +0200	[thread overview]
Message-ID: <53487FE7.2040604@grothoff.org> (raw)
In-Reply-To: <20140411220517.GA1203@amd.pavel.ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]

On 04/12/2014 12:05 AM, Pavel Machek wrote:
> Hi!
> 
>>>> Cryogenic is the result of my Master's Thesis, completed at the Technical University
>>>> of Munich under the supervision of Christian Grothoff. You can find more information
>>>> about Cryogenic at https://gnunet.org/cryogenic
>>>
>>> Do you have any measurements how much power it actually saves?
>>
>> Yes, it depends on the device, but we have demonstrated power
>> savings for two different types of devices using two different
>> measurement setups performed by two independent groups.  Some
>> of the measurements are available on the website, the second
>> set should become available "soon" (but we can already say that
>> for the scenario we measured, the savings are in the same range
>> as before).
> 
> The video I seen.... AFAICT the savings are in <10% range?

For the scenario we scripted, yes. But note that we only
allowed 50% of the packets transmitted to be delayed (a bit).
If you were to increase the allowed delay or allowed a larger
fraction of packets to be delayed, you should see larger savings.

> I seen demo on UDP packets... delayed TCP socket write is probably
> easy, but would API allow delayed TCP connect?

Yes.

> Hmm, but the API needs redoing, anyway, fcntl()?

Depends --- while I like the idea, I did not hear enough to be
certain that having this feature embedded in such a non-modular
way was already the consensus (and I do not see a reasonable
way to change the API this way while maintaining the modularity
of the current code).

[-- Attachment #2: 0x48426C7E.asc --]
[-- Type: application/pgp-keys, Size: 7211 bytes --]

  reply	other threads:[~2014-04-11 23:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-19 15:55 Cryogenic: Enabling Power-Aware Applications on Linux Alejandra Morales
2014-03-20 20:31 ` H. Peter Anvin
2014-03-20 21:06   ` Joe Perches
2014-04-11 10:19 ` Pavel Machek
2014-04-11 18:48   ` Christian Grothoff
2014-04-11 22:05     ` Pavel Machek
2014-04-11 23:51       ` Christian Grothoff [this message]
2014-04-12  0:10         ` David Lang
2014-04-12 11:36         ` Pavel Machek
2014-04-12 22:39           ` H. Peter Anvin

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=53487FE7.2040604@grothoff.org \
    --to=christian@grothoff.org \
    --cc=alejandra.morales@tum.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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