From: Jon Escombe <lists@dresco.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.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 19:14:28 +0100 [thread overview]
Message-ID: <430E0A84.8080809@dresco.co.uk> (raw)
In-Reply-To: <1124967468.21456.6.camel@localhost.localdomain>
Alan Cox wrote:
> @@ -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 ?
I wanted the park command to get in at the head of the queue (behind the
currently executing request).
Contrary to the comments for ide_do_drive_cmd(), ide_next didn't appear
to do anything to achieve this? At least from my initial testing before
I made this change - it could take a second or so for the park command
to be issued if the disk was busy....
Regards,
Jon.
______________________________________________________________
Email via Mailtraq4Free from Enstar (www.mailtraqdirect.co.uk)
next prev parent reply other threads:[~2005-08-25 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1124205914.4855.14.camel@localhost.localdomain>
[not found] ` <20050816200708.GE3425@suse.de>
[not found] ` <20050816200708.GE3425-l3A5Bk7waGM@public.gmane.org>
2005-08-24 21:44 ` Re: HDAPS, Need to park the head for real Jon Escombe
2005-08-25 10:57 ` [Hdaps-devel] " Alan Cox
2005-08-25 18:14 ` Jon Escombe [this message]
[not found] ` <430E0A84.8080809-Xbpc2PeERmvQXOPxS62xeg@public.gmane.org>
2005-08-26 6:49 ` Jens Axboe
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=430E0A84.8080809@dresco.co.uk \
--to=lists@dresco.co.uk \
--cc=abonilla@linuxwireless.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=hdaps-devel@lists.sourceforge.net \
--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).