All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Perkel <marc@perkel.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Making nice niser for system hogging programs
Date: Sat, 01 Oct 2005 20:18:51 -0700	[thread overview]
Message-ID: <433F519B.5070505@perkel.com> (raw)
In-Reply-To: <200510021307.10372.kernel@kolivas.org>



Con Kolivas wrote:

>On Sun, 2 Oct 2005 12:26, Marc Perkel wrote:
>  
>
>>Just a thought -----
>>
>>Programs like cp -a /bigdir /backup and rsync usually bring the server
>>to a crawl no matter how much "nice" you put on them. Is there any way
>>to make "nice" smarter in that it limits io as well as processor usage?
>>If cp and rsyne ran a little slower IO wise then everything else could
>>run too.
>>    
>>
>
>The latest cfq io scheduler supports io nice levels. By default it links the 
>io nice levels to the cpu nice levels so if you use cfq and set your file 
>commands nice 19 they will use as little io priority as possible. Note this 
>only works on the read side but that makes a dramatic difference already.
>
>Cheers
>Con
>  
>

Kewl - so - what version is it in?


-- 
Marc Perkel - marc@perkel.com

Spam Filter: http://www.junkemailfilter.com
    My Blog: http://marc.perkel.com


  reply	other threads:[~2005-10-02  3:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-02  2:26 Making nice niser for system hogging programs Marc Perkel
2005-10-02  3:07 ` Con Kolivas
2005-10-02  3:18   ` Marc Perkel [this message]
2005-10-02  3:38     ` Con Kolivas
2005-10-04 21:26   ` Matt Helsley
2005-10-05 10:02     ` Jens Axboe

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=433F519B.5070505@perkel.com \
    --to=marc@perkel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.