Re: [PATCH 0/2] Fixes for MV_CESA with IDMA or TDMA

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Phil

On 2012-6-19 4:12, Simon Baatz wrote:
I see one effect that I don't fully understand.
Similar to the previous implementation, the system is mostly in
kernel space when accessing an encrypted dm-crypt device:

Today I also compiled the patched 3.5.0-rc3 for another NAS box with MV88F6282-Rev-A0 (LS-WVL), I noticed one thing that when the CESA engine was used, the interrupt number of mv_crypto kept rising, but the interrupt number of mv_tdma was always zero.

$ cat /proc/interrupts
           CPU0
  1:      31296  orion_irq  orion_tick
  5:          2  orion_irq  mv_xor.0
  6:          2  orion_irq  mv_xor.1
  7:          2  orion_irq  mv_xor.2
  8:          2  orion_irq  mv_xor.3
 11:      23763  orion_irq  eth0
 19:          0  orion_irq  ehci_hcd:usb1
 21:       4696  orion_irq  sata_mv
 22:      64907  orion_irq  mv_crypto
 33:        432  orion_irq  serial
 46:         51  orion_irq  mv643xx_eth
 49:          0  orion_irq  mv_tdma
 53:          0  orion_irq  rtc-mv
107:          0         -  GPIO fan alarm
109:          0         -  function
110:          0         -  power-on
111:          0         -  power-auto
Err:          0

Is this normal?

Regards
Cloudy
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel]     [Gnu Classpath]     [Gnu Crypto]     [DM Crypt]     [Netfilter]     [Bugtraq]

  Powered by Linux