From: Bhupesh Sharma <bhsharma@redhat.com>
To: netdev@vger.kernel.org
Cc: bhsharma@redhat.com, bhupesh.linux@gmail.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
aelior@marvell.com, GR-everest-linux-l2@marvell.com,
manishc@marvell.com, davem@davemloft.net, irusskikh@marvell.com
Subject: [PATCH v2 0/2] net: Optimize the qed* allocations inside kdump kernel
Date: Mon, 11 May 2020 15:41:40 +0530 [thread overview]
Message-ID: <1589191902-958-1-git-send-email-bhsharma@redhat.com> (raw)
Changes since v1:
----------------
- v1 can be seen here: http://lists.infradead.org/pipermail/kexec/2020-May/024935.html
- Addressed review comments received on v1:
* Removed unnecessary paranthesis.
* Used a different macro for minimum RX/TX ring count value in kdump
kernel.
Since kdump kernel(s) run under severe memory constraint with the
basic idea being to save the crashdump vmcore reliably when the primary
kernel panics/hangs, large memory allocations done by a network driver
can cause the crashkernel to panic with OOM.
The qed* drivers take up approximately 214MB memory when run in the
kdump kernel with the default configuration settings presently used in
the driver. With an usual crashkernel size of 512M, this allocation
is equal to almost half of the total crashkernel size allocated.
See some logs obtained via memstrack tool (see [1]) below:
dracut-pre-pivot[676]: ======== Report format module_summary: ========
dracut-pre-pivot[676]: Module qed using 149.6MB (2394 pages), peak allocation 149.6MB (2394 pages)
dracut-pre-pivot[676]: Module qede using 65.3MB (1045 pages), peak allocation 65.3MB (1045 pages)
This patchset tries to reduce the overall memory allocation profile of
the qed* driver when they run in the kdump kernel. With these
optimization we can see a saving of approx 85M in the kdump kernel:
dracut-pre-pivot[671]: ======== Report format module_summary: ========
dracut-pre-pivot[671]: Module qed using 124.6MB (1993 pages), peak allocation 124.7MB (1995 pages)
<..snip..>
dracut-pre-pivot[671]: Module qede using 4.6MB (73 pages), peak allocation 4.6MB (74 pages)
And the kdump kernel can save vmcore successfully via both ssh and nfs
interfaces.
This patchset contains two patches:
[PATCH 1/2] - Reduces the default TX and RX ring count in kdump kernel.
[PATCH 2/2] - Disables qed SRIOV feature in kdump kernel (as it is
normally not a supported kdump target for saving
vmcore).
[1]. Memstrack tool: https://github.com/ryncsn/memstrack
Bhupesh Sharma (2):
net: qed*: Reduce RX and TX default ring count when running inside
kdump kernel
net: qed: Disable SRIOV functionality inside kdump kernel
drivers/net/ethernet/qlogic/qed/qed_sriov.h | 10 +++++++---
drivers/net/ethernet/qlogic/qede/qede.h | 2 ++
drivers/net/ethernet/qlogic/qede/qede_main.c | 13 ++++++++++---
3 files changed, 19 insertions(+), 6 deletions(-)
--
2.7.4
next reply other threads:[~2020-05-11 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 10:11 Bhupesh Sharma [this message]
2020-05-11 10:11 ` [PATCH v2 1/2] net: qed*: Reduce RX and TX default ring count when running " Bhupesh Sharma
2020-05-11 10:11 ` [PATCH v2 2/2] net: qed: Disable SRIOV functionality " Bhupesh Sharma
2020-05-11 20:25 ` [PATCH v2 0/2] net: Optimize the qed* allocations " David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1589191902-958-1-git-send-email-bhsharma@redhat.com \
--to=bhsharma@redhat.com \
--cc=GR-everest-linux-l2@marvell.com \
--cc=aelior@marvell.com \
--cc=bhupesh.linux@gmail.com \
--cc=davem@davemloft.net \
--cc=irusskikh@marvell.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®