From: Albert Lee <albertcc@tw.ibm.com>
To: jgarzik@pobox.com
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCHSET] implement and use port_task
Date: Tue, 07 Mar 2006 14:13:43 +0800 [thread overview]
Message-ID: <440D2497.7050504@tw.ibm.com> (raw)
In-Reply-To: <11415401073423-git-send-email-htejun@gmail.com>
Hi Jeff,
>
> 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
>
Something related to the PIO HSM.
After the task renaming by this patchset, the task name is changed from pio_task to port_task.
Should we add polling DMA support to the polling HSM?
It could make the polling HSM more complete.
Polling DMA does no performance gain. However, DMA has crc check,
so it won't be worse than PIO when irq is not working.
Albert
next prev parent reply other threads:[~2006-03-07 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 6:28 [PATCHSET] implement and use port_task Tejun Heo
2006-03-07 6:13 ` Albert Lee [this message]
2006-03-07 7:01 ` Tejun Heo
2006-03-07 7:21 ` Jeff Garzik
2006-03-09 8:39 ` Albert Lee
-- strict thread matches above, loose matches on Subject: below --
2006-03-05 6:29 Tejun Heo
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=440D2497.7050504@tw.ibm.com \
--to=albertcc@tw.ibm.com \
--cc=albertl@mail.com \
--cc=htejun@gmail.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 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).