public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@binarywings.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Kernel Questions
Date: Wed, 23 Jan 2013 19:27:17 +0100	[thread overview]
Message-ID: <51002B85.3010800@binarywings.net> (raw)
In-Reply-To: <20130124002705.16e17b31ba5f165a7da32944@web.de>

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

Am 24.01.2013 00:27, schrieb Silvio Siefke:
> Hello,
> 
> On Tue, 22 Jan 2013 20:48:49 +0100
> Florian Philipp <lists@binarywings.net> wrote:
[...]
>> What kind of workload do we talk about? Properly "niced" and "ioniced"
>> compile jobs? Is the freeze temporary?
> 
> If I run a program, depending on the size the System Freeze for 
> few seconds. When i start emerge -s, emerge --sync, emerge what ever the
> system freeze. Its ever temporary but its make crazy.
> 

Hmm, the last time I encountered something like this, DMA was
deactivated for the hard disk. That happened because the wrong driver
(generic IDE) took over. What raw throughput do you get?
`dd if=/dev/sda of=/dev/null bs=4M count=100 iflag=direct`

>  
>> Odd. Maybe GPU related? Again, does the system recover?
> 
> No GPU is deactivated. When have more then 10 tabs, system hang. 
> 

You mean you have not enabled drm and/or use the generic vesa driver?
Maybe something is trying to use opengl and software emulation slows you
down.

>> Doesn't surprise me. P4 and Atom are both horrible micro architectures.
>> But Atom is also horribly stripped down and has a lower clock frequency.
> 
> Oh, okay i know Atom is shit, but P4. Which architecture is recommended 
> for?
>  

P4s suffer because their pipeline is very long and poorly utilized. In
fact, they can execute fewer instructions per clock tick than a P3.
Anything newer is a vast improvement, especially Core2 and newer.

Regards,
Florian Philipp


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  reply	other threads:[~2013-01-23 18:27 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23 17:53 [gentoo-user] Kernel Questions Silvio Siefke
2013-01-22 18:43 ` Bruce Hill
2013-01-22 19:48   ` Florian Philipp
2013-01-22 22:46     ` Frank Steinmetzger
2013-01-23 23:34       ` Silvio Siefke
2013-01-23  0:46         ` Frank Steinmetzger
2013-01-23 18:31         ` Kevin Chadwick
2013-01-23 22:31           ` Silvio Siefke
2013-01-23 23:27     ` Silvio Siefke
2013-01-23 18:27       ` Florian Philipp [this message]
2013-01-23 18:33         ` Kevin Chadwick
2013-01-24  2:40           ` Frank Steinmetzger
2013-01-24 17:58             ` Paul Hartman
2013-01-23 22:35         ` Silvio Siefke
2013-01-23 23:17   ` Silvio Siefke
2013-01-23  8:30 ` [gentoo-user] " Nicolas Sebrecht
2013-01-24 13:21   ` Silvio Siefke
2013-01-23 13:53     ` William Kenworthy
2013-01-23 15:09       ` Silvio Siefke
2013-01-24 16:12     ` Nicolas Sebrecht
  -- strict thread matches above, loose matches on Subject: below --
2010-08-18 19:30 [gentoo-user] Kernel questions Elmar Hinz
2010-08-18 20:00 ` Nganon
2010-08-18 20:03 ` Andrea Conti
2010-08-18 20:28   ` Paul Hartman
2010-08-19 15:44 ` Florian Philipp
2010-08-19 20:52   ` Elmar Hinz
2010-08-20 14:43   ` Bill Longman
2010-08-20 18:44     ` Marc Joliet
2010-08-20 19:28       ` Bill Longman
2010-08-20 19:35         ` Paul Hartman

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=51002B85.3010800@binarywings.net \
    --to=lists@binarywings.net \
    --cc=gentoo-user@lists.gentoo.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