From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jon Escombe <lists@dresco.co.uk>
Cc: Jens Axboe <axboe@suse.de>,
Alejandro Bonilla Beeche <abonilla@linuxwireless.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
hdaps devel <hdaps-devel@lists.sourceforge.net>,
linux-ide@vger.kernel.org
Subject: Re: [Hdaps-devel] Re: HDAPS, Need to park the head for real
Date: Thu, 25 Aug 2005 11:57:47 +0100 [thread overview]
Message-ID: <1124967468.21456.6.camel@localhost.localdomain> (raw)
In-Reply-To: <430CEA54.7060803@dresco.co.uk>
You need the kernel side timeout. Consider this case
One page of memory holds the parking code
A second page is swapped to disk and holds the resume code
You park the disk
You wakeup
You got to page in the resume code
So you really do want the kernel helping to avoid a deadlock
@@ -1661,6 +1671,9 @@
where = ELEVATOR_INSERT_FRONT;
rq->flags |= REQ_PREEMPT;
}
+ if (action == ide_next)
+ where = ELEVATOR_INSERT_FRONT;
+
__elv_add_request(drive->queue, rq, where, 0);
ide_do_request(hwgroup, IDE_NO_IRQ);
spin_unlock_irqrestore(&ide_lock, flags);
Also puzzles me- why is this needed ?
next prev parent reply other threads:[~2005-08-25 10:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 15:25 HDAPS, Need to park the head for real Alejandro Bonilla Beeche
2005-08-16 15:34 ` Lee Revell
2005-08-16 15:41 ` Alejandro Bonilla Beeche
2005-08-16 20:07 ` Jens Axboe
2005-08-16 23:15 ` Alejandro Bonilla Beeche
2005-08-16 23:29 ` [Hdaps-devel] " Yani Ioannou
2005-08-17 5:53 ` Jens Axboe
2005-08-17 6:23 ` [Hdaps-devel] " Jon Escombe
2005-08-17 7:47 ` Avi Kivity
2005-08-17 7:56 ` Jens Axboe
2005-08-18 20:49 ` Pavel Machek
2005-08-18 21:15 ` Adam Goode
2005-08-18 21:30 ` [Hdaps-devel] " Dave Hansen
2005-08-18 21:38 ` Pavel Machek
2005-08-19 6:36 ` Jens Axboe
2005-08-19 10:05 ` [Hdaps-devel] " Jon Escombe
2005-08-19 10:23 ` Jens Axboe
2005-08-19 12:41 ` Alejandro Bonilla
2005-08-24 21:44 ` Jon Escombe
2005-08-25 10:57 ` Alan Cox [this message]
2005-08-25 18:14 ` Jon Escombe
2005-08-26 6:49 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2005-08-19 11:36 Stefan Rompf
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=1124967468.21456.6.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=abonilla@linuxwireless.org \
--cc=axboe@suse.de \
--cc=hdaps-devel@lists.sourceforge.net \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@dresco.co.uk \
/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