From: Yuri Tikhonov <yur@emcraft.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-raid@vger.kernel.org, linuxppc-dev@ozlabs.org, wd@denx.de,
dzu@denx.de, yanok@emcraft.com
Subject: Re[4]: [PATCH 03/11][v3] async_tx: add support for asynchronous RAID6 recovery operations
Date: Sat, 17 Jan 2009 15:26:57 +0300 [thread overview]
Message-ID: <20244211.20090117152657@emcraft.com> (raw)
In-Reply-To: <e9c3a7c20901161037l6ab42609td327f6f33406e2d@mail.gmail.com>
On Friday, January 16, 2009 you wrote:
> On Fri, Jan 16, 2009 at 4:51 AM, Yuri Tikhonov <yur@emcraft.com> wrote:
>> The reason why I preferred to use async_pq() instead of async_xor()
>> here is to maximize the chance that the whole D+D recovery operation
>> will be handled in one ADMA device, i.e. without channels switch and
>> the latency introduced because of that.
>>
> This should be a function of the async_tx_find_channel implementation.
> The default version tries to keep a chain of operations on one
> channel.
> struct dma_chan *
> __async_tx_find_channel(struct dma_async_tx_descriptor *depend_tx,
> enum dma_transaction_type tx_type)
> {
> /* see if we can keep the chain on one channel */
> if (depend_tx &&
> dma_has_cap(tx_type, depend_tx->chan->device->cap_mask))
> return depend_tx->chan;
> return dma_find_channel(tx_type);
> }
Right. Then I need to update my ADMA driver, and add support for=20
explicit DMA_XOR capability on channels which can process DMA_PQ.
Thanks.
Regards, Yuri
--
Yuri Tikhonov, Senior Software Engineer
Emcraft Systems, www.emcraft.com
prev parent reply other threads:[~2009-01-17 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 0:43 [PATCH 03/11][v3] async_tx: add support for asynchronous RAID6 recovery operations Yuri Tikhonov
2009-01-15 1:06 ` Dan Williams
2009-01-16 11:51 ` Re[2]: " Yuri Tikhonov
2009-01-16 18:37 ` Dan Williams
2009-01-17 12:26 ` Yuri Tikhonov [this message]
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=20244211.20090117152657@emcraft.com \
--to=yur@emcraft.com \
--cc=dan.j.williams@intel.com \
--cc=dzu@denx.de \
--cc=linux-raid@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=wd@denx.de \
--cc=yanok@emcraft.com \
/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).