From: Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl>
To: Tejun Heo <htejun@gmail.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch ide-dev 8/9] make ide_task_ioctl() use REQ_DRIVE_TASKFILE
Date: Sun, 27 Feb 2005 17:31:29 +0100 [thread overview]
Message-ID: <200502271731.29448.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <20050227073608.GA30796@htj.dyndns.org>
On Sunday 27 February 2005 08:36, Tejun Heo wrote:
> Hello, Bartlomiej.
>
> This patch should be modified to use flagged taskfile if the
> task_end_request_fix patch isn't applied. As non-flagged taskfile
> won't return valid result registers, TASK ioctl users won't get the
> correct register output.
Nope, it works just fine because REQ_DRIVE_TASK used only
no-data protocol, please check task_no_data_intr().
> IMHO, this flag-to-get-result-registers thing is way too subtle. How
> about keeping old behavior by just not copying out register outputs in
> ide_taskfile_ioctl() in applicable cases instead of not reading
> registers when ending commands? That is, unless there's some
> noticeable performance impacts I'm not aware of.
This would miss whole point of not _reading_ these registers (IO is slow).
IMHO new flags denoting {in,out} registers should be added (to <linux/ata.h>
to share them with libata) so new code can be sane and old flags would map
on new flags when needed.
next prev parent reply other threads:[~2005-02-28 13:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 14:48 Bartlomiej Zolnierkiewicz
2005-02-27 7:36 ` Tejun Heo
2005-02-27 16:31 ` Bartlomiej Zolnierkiewicz [this message]
2005-02-28 15:24 ` Tejun Heo
2005-02-28 16:14 ` Bartlomiej Zolnierkiewicz
2005-03-01 4:21 ` Tejun Heo
2005-03-01 5:29 ` Tejun Heo
2005-03-01 8:42 ` Bartlomiej Zolnierkiewicz
2005-03-01 9:29 ` Tejun Heo
2005-03-01 9:59 ` Bartlomiej Zolnierkiewicz
2005-03-02 6:08 ` Jeff Garzik
2005-03-02 10:09 ` Bartlomiej Zolnierkiewicz
2005-03-02 19:04 ` Jeff Garzik
2005-03-02 14:20 ` Mark Lord
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=200502271731.29448.bzolnier@elka.pw.edu.pl \
--to=bzolnier@elka.pw.edu.pl \
--cc=htejun@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
all inboxes | Powered by JetHome®