All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Prakash K. Cheemplavam" <prakashkc@gmx.de>
To: Jens Axboe <axboe@suse.de>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, nickpiggin@yahoo.com.au
Subject: Re: Time sliced CFQ io scheduler
Date: Fri, 03 Dec 2004 10:35:49 +0100	[thread overview]
Message-ID: <41B03375.4050702@gmx.de> (raw)
In-Reply-To: <20041203091840.GD10492@suse.de>

[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]

Jens Axboe schrieb:
> On Fri, Dec 03 2004, Prakash K. Cheemplavam wrote:
> 
>>Jens Axboe schrieb:
>>
>>>On Thu, Dec 02 2004, Prakash K. Cheemplavam wrote:
>>>
>>
>>>>0  3   3080   2208   1156 817712    0    0  3592 75624 1326  2289  1 36  
>>>>0 63
>>>>0  3   3080   2664   1156 818240    0    0  5124 15692 1302   992  1 18  
>>>>0 81
>>>>0  3   3080   2580   1160 815832    0    0  4356 155792 1375  1064  1 39  
>>>>0 60
>>>>0  3   3080   2472   1160 817124    0    0  3076 100852 1345  1138  1 23  
>>>>0 76
>>>>2  4   3080   2836   1148 816228    0    0  3336 100412 1352  1379  1 47  
>>>>0 52
>>>>0  4   3080   2708   1144 815964    0    0  3844 48908 1343   871  1 25  
>>>>0 74
>>>>0  3   3080   2748   1152 815984    0    0  3332 71996 1338   843  1 27  
>>>>0 72
>>>
>>>
>>>Can you try with the patch that is in the parent of this thread? The
>>>above doesn't look that bad, although read performance could be better
>>>of course. But try with the patch please, I'm sure it should help you
>>>quite a lot.
>>>
>>
>>It actually got worse: Though the read rate seems accepteble, it is not, as 
>>interactivity is dead while writing. I cannot start porgrammes, other 
>>programmes which want to do i/o pretty much hang. This is only while 
>>writing. While reading there is no such problem.
> 
> 
> Interesting, thanks for testing. I'll run some tests here as well, so
> far only the cases mentioned yesterday have been tested.

BTW, in case it is misread: Above (except the io performance as such) is
no regression: The other schedulers behave the same on my system.


> You could try and bumb the slice period. But I'll experiment and see
> what happens. What is your test case?

[slice bumping] Uhm, is it doable via proc? I haven't seen text docs to
your patch and I am not good at kernel code ;-)

My test case was apkm's one: write 1gb continuesly and try to cat a
several gb big file to /dev/null. At the same time I checked starting
other apps/using my emial client...

For me the problem in mainline has been since quite some time...checked 
till kernel 2.6.7.

Prakash

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-12-03  9:37 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-02 13:04 Time sliced CFQ io scheduler Jens Axboe
2004-12-02 13:48 ` Jens Axboe
2004-12-02 19:48   ` Andrew Morton
2004-12-02 19:52     ` Jens Axboe
2004-12-02 20:19       ` Andrew Morton
2004-12-02 20:19         ` Jens Axboe
2004-12-02 20:34           ` Andrew Morton
2004-12-02 20:37             ` Jens Axboe
2004-12-07 23:11               ` Nick Piggin
2004-12-02 22:18         ` Prakash K. Cheemplavam
2004-12-03  7:01           ` Jens Axboe
2004-12-03  9:12             ` Prakash K. Cheemplavam
2004-12-03  9:18               ` Jens Axboe
2004-12-03  9:35                 ` Prakash K. Cheemplavam [this message]
2004-12-03  9:43                   ` Jens Axboe
2004-12-03  9:26               ` Andrew Morton
2004-12-03  9:34                 ` Prakash K. Cheemplavam
2004-12-03  9:39                 ` Jens Axboe
2004-12-03  9:54                   ` Prakash K. Cheemplavam
     [not found]                   ` <41B03722.5090001@gmx.de>
2004-12-03 10:31                     ` Jens Axboe
2004-12-03 10:38                       ` Jens Axboe
2004-12-03 10:45                         ` Prakash K. Cheemplavam
2004-12-03 10:48                           ` Jens Axboe
2004-12-03 11:27                             ` Prakash K. Cheemplavam
2004-12-03 11:29                               ` Jens Axboe
2004-12-03 11:52                                 ` Prakash K. Cheemplavam
2004-12-08  0:37       ` Andrea Arcangeli
2004-12-08  0:54         ` Nick Piggin
2004-12-08  1:37           ` Andrea Arcangeli
2004-12-08  1:47             ` Nick Piggin
2004-12-08  2:09               ` Andrea Arcangeli
2004-12-08  2:11                 ` Andrew Morton
2004-12-08  2:22                   ` Andrea Arcangeli
2004-12-08  6:52               ` Jens Axboe
2004-12-08  2:00             ` Andrew Morton
2004-12-08  2:08               ` Andrew Morton
2004-12-08  6:55                 ` Jens Axboe
2004-12-08  2:20               ` Andrea Arcangeli
2004-12-08  2:25                 ` Andrew Morton
2004-12-08  2:33                   ` Andrea Arcangeli
2004-12-08  2:33                   ` Nick Piggin
2004-12-08  2:51                     ` Andrea Arcangeli
2004-12-08  3:02                       ` Nick Piggin
2004-12-08  6:58                     ` Jens Axboe
2004-12-08  7:14                       ` Nick Piggin
2004-12-08  7:20                         ` Jens Axboe
2004-12-08  7:29                           ` Nick Piggin
2004-12-08  7:32                             ` Jens Axboe
2004-12-08  7:30                           ` Andrew Morton
2004-12-08  7:36                             ` Jens Axboe
2004-12-08 13:48                         ` Jens Axboe
2004-12-08  6:55               ` Jens Axboe
2004-12-08  7:08                 ` Nick Piggin
2004-12-08  7:11                   ` Jens Axboe
2004-12-08  7:19                     ` Nick Piggin
2004-12-08  7:26                       ` Jens Axboe
2004-12-08  9:35                         ` Jens Axboe
2004-12-08 10:08                           ` Jens Axboe
2004-12-08 12:47                           ` Jens Axboe
2004-12-08 10:52                 ` Helge Hafting
2004-12-08 10:49                   ` Jens Axboe
2004-12-08  6:49           ` Jens Axboe
2004-12-02 14:28 ` Giuliano Pochini
2004-12-02 14:41   ` Jens Axboe
2004-12-04 13:05     ` Giuliano Pochini
  -- strict thread matches above, loose matches on Subject: below --
2004-12-03 20:52 Chuck Ebbert

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=41B03375.4050702@gmx.de \
    --to=prakashkc@gmx.de \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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.