From: Bill Davidsen <davidsen@tmr.com>
To: Linda Walsh <lkml@tlinx.org>
Cc: Lukas Hejtmanek <xhejtman@ics.muni.cz>, linux-kernel@vger.kernel.org
Subject: Re: Disk schedulers
Date: Thu, 28 Feb 2008 12:14:27 -0500 [thread overview]
Message-ID: <47C6EBF3.8080703@tmr.com> (raw)
In-Reply-To: <47B88D18.8060907@tlinx.org>
Linda Walsh wrote:
> You didn't say anything about #processors or speed, nor
> did you say anything about your hard disk's raw-io ability.
> You also didn't mention what kernel version or whether or not
> you were using the new UID-group cpu scheduler in 2.6.24 (which likes
> to default to 'on'; not a great choice for single-user, desktop-type
> machines, if I understand its grouping policy).
> Are you sure neither end of the copy is cpu-bound on ssh/scp
> encrypt/decrypt calculations? It might not just be inability
> to read from disk, but low cpu availability. Scp can be alot
> more CPU intensive than you would expect... Just something to
> consider...
>
Good point, and may I note that you *can* choose your encryption, I use
'blowfish' for normal operation, since I have some faitly slow machines
with a Gbit net between them.
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
prev parent reply other threads:[~2008-02-28 17:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-14 16:21 Disk schedulers Lukas Hejtmanek
2008-02-15 0:02 ` Tejun Heo
2008-02-15 10:09 ` Lukas Hejtmanek
2008-02-15 14:42 ` Jan Engelhardt
2008-02-15 14:57 ` Prakash Punnoor
2008-02-15 17:11 ` Zan Lynx
2008-02-15 21:32 ` FD Cami
2008-02-16 16:13 ` Lukas Hejtmanek
2008-02-20 17:04 ` Zdenek Kabelac
2008-02-15 15:59 ` Lukas Hejtmanek
2008-02-15 16:22 ` Jeffrey E. Hundstad
2008-02-15 17:36 ` Roger Heflin
2008-02-15 17:24 ` Paulo Marques
2008-02-16 16:15 ` Lukas Hejtmanek
2008-02-16 17:20 ` Pavel Machek
2008-02-20 18:48 ` Lukas Hejtmanek
2008-02-21 23:50 ` Giuliano Pochini
2008-02-17 19:38 ` Linda Walsh
2008-02-28 17:14 ` Bill Davidsen [this message]
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=47C6EBF3.8080703@tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.org \
--cc=xhejtman@ics.muni.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