public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ionice kills vanilla 2.6.0-test9 was [Re: [PATCH] cfq + io priorities (fwd)]
Date: Fri, 21 Nov 2003 21:14:08 +0100	[thread overview]
Message-ID: <20031121201408.GF6616@suse.de> (raw)
In-Reply-To: <20031121153900.GA193@elf.ucw.cz>

On Fri, Nov 21 2003, Pavel Machek wrote:
> Hi!
> 
> > > I'm attaching the simple ionice tool. It's used as follows:
> > 
> > Here's one that works, sorry about that. To compile:
> > 
> > # gcc -Wall -D__X86 -o ionice ionice.c
> > 
> > or other define for PPC or X86_64.
> 
> Well, did that, run it on vanilla kernel, and it kills the
> machine. Can someone reproduce it?

I saw that on ppc too, btw, didn't trace it yet. But there definitely is
a problem with calling syscalls that don't exist.

> [What is needed to start using cfq? Is your patch, this utility and
> elevator=cfq enough?]

Yes, that is it. Your result may vary though, I have a newer cfq that's
almost ready for release that fixes varies performance problems.

-- 
Jens Axboe


  reply	other threads:[~2003-11-21 20:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031113124510.GZ643@openzaurus.ucw.cz>
2003-11-21 15:39 ` ionice kills vanilla 2.6.0-test9 was [Re: [PATCH] cfq + io priorities (fwd)] Pavel Machek
2003-11-21 20:14   ` Jens Axboe [this message]
2003-11-24  3:44     ` Benjamin Herrenschmidt
2003-11-21 22:45   ` Linus Torvalds
2003-11-21 23:05     ` Linus Torvalds
2003-11-21 23:33       ` Linus Torvalds
2003-11-22 11:04         ` Jamie Lokier
2003-11-22  4:42       ` Alan Modra
2003-11-26 20:06       ` Nick Clifton
2003-11-26 20:23         ` Jakub Jelinek

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=20031121201408.GF6616@suse.de \
    --to=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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