public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stefan G. Weichinger" <lists@xunil.at>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Slow network transfers ... lost interrupts because of clocksource?
Date: Mon, 30 Sep 2013 19:36:35 +0200	[thread overview]
Message-ID: <5249B6A3.1070107@xunil.at> (raw)
In-Reply-To: <5249AFD9.3050100@googlemail.com>

Am 30.09.2013 19:07, schrieb Volker Armin Hemmann:
> Am 30.09.2013 11:54, schrieb Stefan G. Weichinger:
>> Am 29.09.2013 16:37, schrieb Stefan G. Weichinger:
>>> Am 27.09.2013 17:55, schrieb Volker Armin Hemmann:
>>>
>>>>> What direction to go? force or disable HPET?
>>>>>
>>>>>
>>>> neither
>>> And what to do to avoid those lost interrupts?
>> Is there no good suggestion for this?
>>
>>
>>
>>
>>
> let the kernel figure out the best clocksource for you?
> 
> if you have a real problem with lost interrupts, go to lkml.

I am gonna reboot the system without forcing any clocksource after my
current "emerge -e @system" (I did that to fit the transferred VM-image
to the given hardware/CPU). And I will maybe upgrade to 3.10.7-r1 as well.

What is the best way to transfer multi-GB-files in LAN? I don't really
need encryption here ...

thanks, Stefan



  reply	other threads:[~2013-09-30 17:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27 10:33 [gentoo-user] Slow network transfers ... lost interrupts because of clocksource? Stefan G. Weichinger
2013-09-27 13:02 ` [gentoo-user] " Nicolas Sebrecht
2013-09-27 13:06   ` Stefan G. Weichinger
2013-09-27 13:18     ` Nicolas Sebrecht
2013-09-27 15:05       ` Stefan G. Weichinger
2013-09-27 15:55 ` [gentoo-user] " Volker Armin Hemmann
2013-09-29 14:37   ` Stefan G. Weichinger
2013-09-30  9:54     ` Stefan G. Weichinger
2013-09-30 17:07       ` Volker Armin Hemmann
2013-09-30 17:36         ` Stefan G. Weichinger [this message]
2013-09-30 17:44           ` Bruce Hill
2013-09-30 17:46           ` Bruce Hill
2013-09-30 17:50             ` Stefan G. Weichinger
2013-09-30 18:23         ` Stefan G. Weichinger
2013-09-30 20:03           ` Stefan G. Weichinger
2013-10-01  8:26             ` Stefan G. Weichinger
2013-10-01 12:32               ` [gentoo-user] " Nicolas Sebrecht
2013-10-01 14:00                 ` Stefan G. Weichinger
2013-10-01 19:21                   ` Stefan G. Weichinger
2013-10-09 14:53                     ` Stefan G. Weichinger
2013-10-09 18:20                       ` Nicolas Sebrecht
2013-10-09 19:17                         ` Stefan G. Weichinger
2013-10-09 19:57                           ` Volker Armin Hemmann
2013-10-09 20:05                             ` Stefan G. Weichinger
2013-10-09 20:40                               ` Stefan G. Weichinger
2013-10-09 22:11                                 ` Stefan G. Weichinger
2013-10-09 22:18                                   ` Stefan G. Weichinger
2013-10-10 12:20                                     ` Bruce Hill
2013-10-10 14:38                                       ` Stefan G. Weichinger
2013-10-14  6:23                                         ` Stefan G. Weichinger
2013-10-14 17:21                                           ` Volker Armin Hemmann

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=5249B6A3.1070107@xunil.at \
    --to=lists@xunil.at \
    --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