diff options
author | David S. Miller | 2014-02-26 15:28:08 -0500 |
---|---|---|
committer | David S. Miller | 2014-02-26 15:28:08 -0500 |
commit | f2ea0cfd6b5fb7daf4cf48bdc364f1cf9ef55d0c (patch) | |
tree | 0a543a0f2f3717659320a29201ac14f6ecf25c6b /net/core/net-sysfs.c | |
parent | 8e165e20348b53583f6c6cb45865b89209f4aa13 (diff) | |
parent | 94d9de3cf7b7902253e65d7aef30f2db051c1ac6 (diff) |
Merge branch 'bnx2x'
Michal Schmidt says:
====================
bnx2x: minimize RAM usage in kdump
kdump kernels usually have only a small amount of memory reserved.
bnx2x can be memory-hungry. Let's minimize its memory usage when
running in kdump.
I detect kdump by looking at the "reset_devices" flag. A couple of
storage drivers (cciss, hpsa) use it for the same purpose. I am not sure
this is the best way to solve the problem, but it works.
Should it be made more generic by, say, looking at the total amount
of lowmem instead? Not using TPA by default when lowmem is small and/or
defaulting to fewer queues would help 32bit systems where a driver for
a multi-function multi-queue NIC can consume a significant amount
of available memory. Or do we want no such heuristics?
Is this something to consider doing for other network drivers too?
====================
Acked-by: Ariel Elior <ariele@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/core/net-sysfs.c')
0 files changed, 0 insertions, 0 deletions