mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Mihai Moldovan" <ionic@ionic.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Multiple minor glitches with 2.6.27.* and linux-NEXT
Date: Fri, 19 Dec 2008 14:19:25 -0800	[thread overview]
Message-ID: <4807377b0812191419k42b7749chff70f0e217a24cfe@mail.gmail.com> (raw)
In-Reply-To: <494BABB0.8050309@ionic.de>

On Fri, Dec 19, 2008 at 6:12 AM, Mihai Moldovan <ionic@ionic.de> wrote:
> First of all, will the changes to e1000e be integrated in Linux 2.6.28
> as soon as it is released? 2.6.27 does not detect my onboard NIC, whilst
> Linux-NEXT does. Some basic information about this:

2.6.28 should have support for 8086/10de.

<big snip>

> Might anyone here be so kind to explain me whether disabling specific
> Cores of an Intel(R)™ Core2Quad CPU completely ...
>
>  - is possible? I am not quite sure whether this would work at all.
>  - would indeed safe power/lower the power consumption? Logically
> disabling cores does safe hardly any power. :)

I'm not the best person to answer, but if you enable TICKLESS kernel
and ACPI power states (and run one of the powersave governors,
basically treating your desktop like a laptop) then your CPUs will use
very little power.

You should be able to get an idea of the power being used by your
system by seeing how much time it spends in C1/C2/C3, using the
powertop application from http://www.lesswatts.org/projects/powertop/

it will also give suggestions about how to optimize your system.  Why
disable cores when the system will effectively do it for you?  If
you're really serious about conserving power, get a power meter that
goes between your power plug and the wall and measure the wattage
being consumed by your system.

  reply	other threads:[~2008-12-19 22:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-19 14:12 Mihai Moldovan
2008-12-19 22:19 ` Jesse Brandeburg [this message]
2008-12-19 23:18   ` Mihai Moldovan

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=4807377b0812191419k42b7749chff70f0e217a24cfe@mail.gmail.com \
    --to=jesse.brandeburg@gmail.com \
    --cc=ionic@ionic.de \
    --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

all inboxes | Powered by JetHome®