Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: liweihang <liweihang@huawei.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"jgg@ziepe.ca" <jgg@ziepe.ca>,
	"linuxarm@openeuler.org" <linuxarm@openeuler.org>
Subject: Re: Is it ok to use debugfs to dump some ucontext-level driver-defined info?
Date: Thu, 31 Dec 2020 09:59:07 +0200	[thread overview]
Message-ID: <20201231075907.GD6438@unreal> (raw)
In-Reply-To: <d681bc1cad0e4726806aeb46f240d07d@huawei.com>

On Tue, Dec 29, 2020 at 01:31:39PM +0000, liweihang wrote:
> Hi all,
>
> We want to dump some hns driver-defined information that belongs to a
> process to keep track of current memory usage. For example, there is
> a ucontext-level(process-level) memory pool to store WQE which is
> shared by a lot of QPs, we want to record and query which QPs are using
> this pool and how much space each QP is using.
>
> rdmatool don't have a ucontext-level resource tracking currently, is it
> ok to achieve that through debugfs?
>
> This may looks like:
>
> $ echo 1 > <dbgfs_dir>/hns_roce/hns_0/<pid>/qp
> QPN        Total(kB)  SQ(kB)     SGE(kB)    RQ(kB)
> 110        6400       256        2048       4096
> 118        6400       256        2048       0
>
> Or should it be achieved in rdmatool?

I think so, because PID != ucontext. Why can't it be presented as QP
attribute? Can you please send "rdmatool" example?

Thanks

>
> Thanks
> Weihang

  reply	other threads:[~2020-12-31  8:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-29 13:31 Is it ok to use debugfs to dump some ucontext-level driver-defined info? liweihang
2020-12-31  7:59 ` Leon Romanovsky [this message]
2020-12-31  9:36   ` liweihang
2020-12-31 10:38     ` Leon Romanovsky
2021-01-05  3:15       ` liweihang
2021-01-05  6:46         ` Leon Romanovsky

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=20201231075907.GD6438@unreal \
    --to=leon@kernel.org \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linuxarm@openeuler.org \
    --cc=liweihang@huawei.com \
    /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