Hello Adam,
Thank you for you helpful answer.
I tried what you suggested: I copied the driver files from the 3.2.32
source tree , and put them in a 3.4.16 tree before recompiling.
The result (3.4.16 kernel with 3.2.32 driver) compiled perfectly well,
but unhappily it has the same problem than before, with a disk transfer
rate around 1 Mb/s .
So, my conclusion is the problem doesn't come from the driver itself,
but from something else in the kernel, which changed between versions
3.2.x and 3.3.x , and changes the behaviour of Megaraid driver.
Have you another suggestion? I've tried many combinations of options
memory, interrupts, etc. related but without success.
Have a nice day - hope to hear from you soon.
regards,
Jeremie
On 02/11/2012 21:54, adam radford wrote:
On Fri, Nov 2, 2012 at 3:06 AM, Jérémie GUILLAUME
<jeremie.guillaume-prestataire@xxxxxxxxxxxxxxxxxxx> wrote:
...
with 3.2.x kernels
------------------
- no problem occurs ; we have good data transfers , even in 64 Gb High
Memory mode.
Jeremie,
The megaraid_sas driver changes from 3.2 kernel, version 6.12-rc1, to
3.3 kernel, version 6.14-rc1 are quite minimal and would not affect
any 32-bit 64 GB memory mode/PAE mode.
Feel free to copy the following files from your 3.2 kernel source into
your 3.3 kernel source:
drivers/scsi/megaraid/megaraid_sas_base.c megaraid_sas.h
megaraid_sas_fusion.c megaraid_sas_fusion.h megaraid_sas_fp.c
then rebuild your kernel and modules. That should help you determine
if there was actually a megaraid_sas driver related performance
regression, since you will have the exact same driver code running for
both kernels.
-Adam
--
Cellule ADSI - Crédit Agricole SA
-
Jérémie GUILLAUME
Tél : 01 57 72 02 77
jeremie.guillaume-prestataire@xxxxxxxxxxxxxxxxxxx
--
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
