From: Con Kolivas <kernel@kolivas.org>
To: Marc Perkel <marc@perkel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Making nice niser for system hogging programs
Date: Sun, 2 Oct 2005 13:38:19 +1000 [thread overview]
Message-ID: <200510021338.22326.kernel@kolivas.org> (raw)
In-Reply-To: <433F519B.5070505@perkel.com>
[-- Attachment #1: Type: text/plain, Size: 1327 bytes --]
On Sun, 2 Oct 2005 13:18, Marc Perkel wrote:
> 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.
>
> Kewl - so - what version is it in?
2.6.13 already has it. Note that the io priority is only inherited when a
process first starts so doing renice to something already running will only
change the cpu nice, not the ionice. You can do that on the fly using the
ionice application. If you look in the kernel source in
Documentation/block/ioprio.txt you'll find the source to ionice.c
Cheers,
Con
P.S. It is considered routine to reply-to-all when posting to lkml and not
stripping anybody on the cc list.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-02 3:38 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
2005-10-02 3:38 ` Con Kolivas [this message]
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=200510021338.22326.kernel@kolivas.org \
--to=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@perkel.com \
/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