From: Tejun Heo <htejun@gmail.com>
To: jgarzik@pobox.com, albertcc@tw.ibm.com,
linux-ide@vger.kernel.org, htejun@gmail.com
Subject: [PATCHSET] implement and use port_task
Date: Sun, 5 Mar 2006 15:29:09 +0900 [thread overview]
Message-ID: <1141540149886-git-send-email-htejun@gmail.com> (raw)
In-Reply-To:
Hello, Jeff and Albert.
This patchset implements port_task and replace pio_task and
packet_task with it. port_task isn't very different from pio_task or
packet_task - it's straight forward generalization. The port_task is
a per-port task avaliable to low level drivers which is managed by
libata core layer.
Differences from pio/packet task.
* Not limited to PIO HSM implementation. Other drivers can use it.
* Synchronization against EH core layer is done within libata core
layer, not in PIO HSM implementation (ata_qc_timeout()).
Thanks.
--
tejun
next reply other threads:[~2006-03-05 6:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 6:29 Tejun Heo [this message]
2006-03-05 6:29 ` [PATCH 4/4] libata: rename ATA_FLAG_FLUSH_PIO_TASK to ATA_FLAG_FLUSH_PORT_TASK Tejun Heo
2006-03-05 6:29 ` [PATCH 2/4] libata: convert pio_task and packet_task to port_task Tejun Heo
2006-03-11 23:43 ` Jeff Garzik
2006-03-05 6:29 ` [PATCH 1/4] libata: implement port_task Tejun Heo
2006-03-05 16:09 ` Jeff Garzik
2006-03-05 16:23 ` Tejun Heo
2006-03-05 6:29 ` [PATCH 3/4] libata: kill unused pio_task and packet_task Tejun Heo
-- strict thread matches above, loose matches on Subject: below --
2006-03-05 6:28 [PATCHSET] implement and use port_task Tejun Heo
2006-03-07 6:13 ` Albert Lee
2006-03-07 7:01 ` Tejun Heo
2006-03-07 7:21 ` Jeff Garzik
2006-03-09 8:39 ` Albert Lee
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=1141540149886-git-send-email-htejun@gmail.com \
--to=htejun@gmail.com \
--cc=albertcc@tw.ibm.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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.