From: Lee Revell <rlrevell@joe-job.com>
To: Takashi Ikebe <ikebe.takashi@lab.ntt.co.jp>
Cc: Jens Axboe <axboe@suse.de>,
andrea@suse.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Real-time problem due to IO congestion.
Date: Fri, 10 Jun 2005 14:26:46 -0400 [thread overview]
Message-ID: <1118428006.6423.5.camel@mindpipe> (raw)
In-Reply-To: <42A94611.8070502@lab.ntt.co.jp>
On Fri, 2005-06-10 at 16:49 +0900, Takashi Ikebe wrote:
> Jens Axboe wrote:
> > On Fri, Jun 10 2005, Takashi Ikebe wrote:
> >
> > This basically needs io priorities to work, so that request allocation
> > is prioritized as well. I didn't actually add request allocation groups
> > in the cfq-ts posted with priority support, however I have some patches
> > from years ago that did so. I'll see if I can find the time to brush
> > those off.
> >
>
> As you and andrew said, basically application based approach seems
> reasonable,
> but I'm so interesting your patch, if you have time, please show me :-)
Take a look at the lock-free ringbuffers in JACK. No point reinventing
the wheel...
I think it's a bit strange that the disk IO issue comes up so often in
these RT discussions, it's something of a red herring, because there's
rarely an RT constraint in getting the data to disk; the RT constraint
is in getting the data from the device to memory.
Lee
next prev parent reply other threads:[~2005-06-10 18:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 4:55 Real-time problem due to IO congestion Takashi Ikebe
2005-06-10 6:24 ` Jens Axboe
2005-06-10 7:49 ` Takashi Ikebe
2005-06-10 18:26 ` Lee Revell [this message]
2005-06-10 6:42 ` Andrew Morton
2005-06-10 7:13 ` Takashi Ikebe
2005-06-10 7:21 ` Jens Axboe
2005-06-10 20:25 ` Helge Hafting
2005-06-13 1:46 ` Takashi Ikebe
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=1118428006.6423.5.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=andrea@suse.de \
--cc=axboe@suse.de \
--cc=ikebe.takashi@lab.ntt.co.jp \
--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.