Skip to content

K
Kernel

openeuler / Kernel
1 年多 前同步成功

通知 8
Star 0
Fork 0
K
Kernel
切换分支/标签
  1. 16 2月, 2010 19 次提交
  3. 04 2月, 2010 1 次提交
  5. 17 1月, 2010 2 次提交
  7. 07 1月, 2010 1 次提交
  9. 23 12月, 2009 1 次提交
  11. 18 12月, 2009 1 次提交
  13. 23 11月, 2009 2 次提交
  15. 20 11月, 2009 1 次提交
    • D
      async_tx: build-time toggling of async_{syndrome,xor}_val dma support · 7b3cc2b1
      由 Dan Williams 提交于 
      ioat3.2 does not support asynchronous error notifications which makes
the driver experience latencies when non-zero pq validate results are
expected.  Provide a mechanism for turning off async_xor_val and
async_syndrome_val via Kconfig.  This approach is generally useful for
any driver that specifies ASYNC_TX_DISABLE_CHANNEL_SWITCH and would like
to force the async_tx api to fall back to the synchronous path for
certain operations.
Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      7b3cc2b1
  17. 19 11月, 2009 1 次提交
  19. 16 11月, 2009 1 次提交
    • H
      crypto: gcm - fix another complete call in complete fuction · 62c5593a
      由 Huang Ying 提交于 
      The flow of the complete function (xxx_done) in gcm.c is as follow:

void complete(struct crypto_async_request *areq, int err)
{
	struct aead_request *req = areq->data;

	if (!err) {
		err = async_next_step();
		if (err == -EINPROGRESS || err == -EBUSY)
			return;
	}

	complete_for_next_step(areq, err);
}

But *areq may be destroyed in async_next_step(), this makes
complete_for_next_step() can not work properly. To fix this, one of
following methods is used for each complete function.

- Add a __complete() for each complete(), which accept struct
  aead_request *req instead of areq, so avoid using areq after it is
  destroyed.

- Expand complete_for_next_step().

The fixing method is based on the idea of Herbert Xu.
Signed-off-by: NHuang Ying <ying.huang@intel.com>
Signed-off-by: NHerbert Xu <herbert@gondor.apana.org.au>
      62c5593a
  21. 12 11月, 2009 1 次提交
  23. 27 10月, 2009 3 次提交
  25. 20 10月, 2009 3 次提交
    • D
      async_tx: fix asynchronous raid6 recovery for ddf layouts · da17bf43
      由 Dan Williams 提交于 
      The raid6 recovery code currently requires special handling of the
4-disk and 5-disk recovery scenarios for the native layout.  Quoting
from commit 0a82a623:

     In these situations the default N-disk algorithm will present
     0-source or 1-source operations to dma devices.  To cover for
     dma devices where the minimum source count is 2 we implement
     4-disk and 5-disk handling in the recovery code.

The ddf layout presents disks=6 and disks=7 to the recovery code in
these situations.  Instead of looking at the number of disks count the
number of non-zero sources in the list and call the special case code
when the number of non-failed sources is 0 or 1.

[neilb@suse.de: replace 'ddf' flag with counting good sources]
Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      da17bf43
    • D
      async_pq: rename scribble page · 030b0772
      由 Dan Williams 提交于 
      The global scribble page is used as a temporary destination buffer when
disabling the P or Q result is requested.  The local scribble buffer
contains memory for performing address conversions.  Rename the global
variable to avoid confusion.
Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      030b0772
    • D
      async_pq: kill a stray dma_map() call and other cleanups · 5676470f
      由 Dan Williams 提交于 
      - update the kernel doc for async_syndrome to indicate what NULL in the
  source list means
- whitespace fixups
Signed-off-by: NDan Williams <dan.j.williams@intel.com>
      5676470f
  27. 19 10月, 2009 3 次提交