linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Doubts on async_tx xor offload for raid5/6
@ 2016-06-02  6:24 Vikas Aggarwal
  2016-06-07  7:19 ` Vinod Koul
  0 siblings, 1 reply; 2+ messages in thread
From: Vikas Aggarwal @ 2016-06-02  6:24 UTC (permalink / raw)
  To: linux-raid, dmaengine

Hi  list,
Will appreciate if someone can clear my doubts with "some theoretical
examples". I am trying to improve XOR/GF offload for a multi-core SoC
(currently it has single XOR/GF  channel).

1) What is the purpose of device_prep_dma_interrupt  callback ?

2) My driver currently polls for posting  xor  completions
(dma_cookie_complete) and does'nt use  device_prep_dma_interrupt
callback at all.  What  gains/loss in terms of  latency/cpu
idleness/WRITE throughput  I can expect  by implementing this callback
in my async_tx driver.

3) Purpose of DMA_ACK as I read - it is  for higher layers to inform
dma driver that descriptors can now be freed. Can someone explain this
with an example as applicable with raid5/6 clients.

4) With example - why dma_run_dependencies(tx) needed  after the
hardware engine post completion for a descriptor.

5) Purpose of  tx->callback(cb_arg) - again with an example from a
raid5/6 offload perspective.

I want to use offload engine efficiently with multithreaded raid5/6.

I tried to dig through dma/drivers, crypto/async_xor.c, online
archives, linux/Documentation etc but could not get satisfactory
answers. Added two mail-lists as saw issues being discussed on both
ones.

Thanks and
Best Regards
Vikas Aggarwal

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-06-07  7:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-06-02  6:24 Doubts on async_tx xor offload for raid5/6 Vikas Aggarwal
2016-06-07  7:19 ` Vinod Koul

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).