linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajasekhar Pulluru <pullururajasekhar@gmail.com>
To: linux-raid@vger.kernel.org
Subject: async_tx and RAID HW xor engine
Date: Mon, 30 Apr 2012 15:35:30 +0530	[thread overview]
Message-ID: <CAGA5_H55asVEekOd1ae2OjkK07W5Okf1iTCg10oRSX4+M7FLEA@mail.gmail.com> (raw)

Hi,

I am trying to understand how are hardware xor engine's utilized by
async_tx module. I don't get the exact link that connects async_tx and
hardware xor engine.
Could someone help me understand it.

Registration of a RAID HW XOR engine happens in
drivers/dma/<soc-xor.c> using dma_async_device_register(). Does this
registration function connect the async_tx api's
to use the HW XOR engine? Or is there anything we need to support to
make async_tx api's to take advantage of the hardware XOR engine?

Thanks & Regards,
Rajasekhar

             reply	other threads:[~2012-04-30 10:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 10:05 Rajasekhar Pulluru [this message]
2012-04-30 20:31 ` async_tx and RAID HW xor engine Dan Williams
2012-05-01  0:49   ` NeilBrown
2012-05-02 19:11     ` Dan Williams

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=CAGA5_H55asVEekOd1ae2OjkK07W5Okf1iTCg10oRSX4+M7FLEA@mail.gmail.com \
    --to=pullururajasekhar@gmail.com \
    --cc=linux-raid@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).