Thread (28 messages) 28 messages, 6 authors, 2017-01-30
STALE3451d
Revisions (16)
  1. v1 [diff vs current]
  2. v2 [diff vs current]
  3. v3 [diff vs current]
  4. v4 [diff vs current]
  5. v4 [diff vs current]
  6. v4 [diff vs current]
  7. v4 [diff vs current]
  8. v4 [diff vs current]
  9. v4 [diff vs current]
  10. v4 [diff vs current]
  11. v4 current
  12. v4 [diff vs current]
  13. v5 [diff vs current]
  14. v5 [diff vs current]
  15. v5 [diff vs current]
  16. v6 [diff vs current]

[PATCH v4 2/6] block: Add Sed-opal library

From: hch@infradead.org (Christoph Hellwig)
Date: 2017-01-24 07:46:22

On Thu, Jan 19, 2017@11:28:40AM -0700, Scott Bauer wrote:
Just let alloc_opal_dev kzalloc normally and do no alignment. It would then
be up to the drivers to move the data from the buffer to a bounce buffer,
that is aligned, in the send/recv functions before sending down to the controller.

Both are easy to implement but we wanted to see if anyone had other ideas or liked
one over the other.
Option two works, and there won't be any bounce buffering as kmalloc
allocations are always naturally and dma boundary aligned.

Option three is to simply drop the alignment and let the block
layer bounce buffer if needed.

Either two or three are fine with me.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help