From: Tejun Heo <htejun@gmail.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: macbook pro dvd playback after suspend Buffer I/O error
Date: Thu, 12 Jun 2008 15:59:32 +0900 [thread overview]
Message-ID: <4850C954.60805@gmail.com> (raw)
In-Reply-To: <dd18b0c30806112336ma74115cta1923f7b08dcc2d@mail.gmail.com>
Justin Mattock wrote:
> Yeah, take you're time. Maybe it's easier to have mplayer or which
> ever media player wait for the drive. i.g.
> under OSX, the media player pauses until the drive does it's thing,
> and then resumes.(but this would be for the suspend aspect)
> As for the live distro part I'd have to think as well. Let me know
> what you think.
For apps which know they're accessing cd or dvd (probably using sg
commands), asking for TUR test after resume could be acceptable but apps
getting -EIO on read(2) because of intervening suspend/resume cycle is
just not right. The problem is that readiness waiting can take quite
some time and under the current architecture, that can make resume take
much longer or block IOs to other devices on the same port. :-(
--
tejun
next prev parent reply other threads:[~2008-06-12 6:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <dd18b0c30804032207u36bd1f43l358e9949f0c94f79@mail.gmail.com>
2008-04-04 8:21 ` macbook pro dvd playback after suspend Buffer I/O error Andrew Morton
2008-04-04 15:05 ` Justin Mattock
2008-06-11 2:00 ` Tejun Heo
2008-06-11 7:45 ` Justin Mattock
2008-06-11 18:31 ` Justin Mattock
2008-06-11 21:51 ` Tejun Heo
2008-06-11 22:27 ` Justin Mattock
2008-06-12 1:18 ` Tejun Heo
2008-06-12 2:10 ` Justin Mattock
2008-06-12 2:13 ` Justin Mattock
2008-06-12 4:15 ` Tejun Heo
2008-06-12 5:22 ` Justin Mattock
2008-06-12 6:15 ` Justin Mattock
2008-06-12 6:26 ` Tejun Heo
2008-06-12 6:36 ` Justin Mattock
2008-06-12 6:59 ` Tejun Heo [this message]
2008-06-12 7:45 ` Justin Mattock
2008-04-04 19:02 Justin Mattock
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=4850C954.60805@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=justinmattock@gmail.com \
--cc=linux-ide@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).