From: Leon Romanovsky <leon@kernel.org>
To: Michal Kalderon <Michal.Kalderon@cavium.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, dledford@redhat.com,
jgg@mellanox.com, linux-rdma@vger.kernel.org,
Ariel Elior <Ariel.Elior@cavium.com>
Subject: Re: [PATCH net] qed: Free RoCE ILT Memory on rmmod qedr
Date: Mon, 5 Mar 2018 11:41:28 +0200 [thread overview]
Message-ID: <20180305094128.GI15340@mtr-leonro.local> (raw)
In-Reply-To: <1520240651-11308-1-git-send-email-Michal.Kalderon@cavium.com>
[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]
On Mon, Mar 05, 2018 at 11:04:11AM +0200, Michal Kalderon wrote:
> Rdma requires ILT Memory to be allocated for it's QPs.
> Each ILT entry points to a page used by several Rdma QPs.
> To avoid allocating all the memory in advance, the rdma
> implementation dynamically allocates memory as more QPs are
> added, however it does not dynamically free the memory.
> The memory should have been freed on rmmod qedr, but isn't.
> This patch adds the memory freeing on rmmod qedr (currently
> it will be freed with qed is removed).
>
> An outcome of this bug, is that if qedr is unloaded and loaded
> without unloaded qed, there will be no more RoCE traffic.
>
> The reason these are related, is that the logic of detecting the
> first QP ever opened is by asking whether ILT memory for RoCE has
> been allocated.
>
> In addition, this patch modifies freeing of the Task context to
> always use the PROTOCOLID_ROCE and not the protocol passed,
> this is because task context for iWARP and ROCE both use the
> ROCE protocol id, as opposed to the connection context.
>
> Fixes: dbb799c39717e7b7
Your fixes line was truncated.
Thanks
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-03-05 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 9:04 [PATCH net] qed: Free RoCE ILT Memory on rmmod qedr Michal Kalderon
2018-03-05 9:41 ` Leon Romanovsky [this message]
2018-03-05 9:50 ` Kalderon, Michal
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=20180305094128.GI15340@mtr-leonro.local \
--to=leon@kernel.org \
--cc=Ariel.Elior@cavium.com \
--cc=Michal.Kalderon@cavium.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=jgg@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--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