public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: dumping queue state
Date: Wed, 20 Dec 2017 09:53:33 -0600	[thread overview]
Message-ID: <00a701d379aa$b098ee10$11caca30$@opengridcomputing.com> (raw)

Hey,

I have a need to provide tools for customers to gather runtime state for an
rdma device.   Say, when an application is stuck waiting for some completion
or other rdma event.   This includes hw/fw state of course, and equally as
important, rdma object sw state.  Is debugfs the correct way to export this
sw state?  The data is quite large potentially; each QP, its structures, the
dma queue memory, etc.  Ditto for CQs.  Also MR state, etc etc.  It seems
that would be overloading debugfs to me.  Currently the hw/fw state is being
gathered via ethtool dump commands (--get-dump, --register-dump,
--eeprom-dump).  I am considering using the ethtool --get-dump method for
the low level driver to also include dumping the rdma queue state for the
device.   Is that a reasonable approach?

Any thoughts/suggestions? 

Thanks in advance,

Steve.


---
This email has been checked for viruses by AVG.
http://www.avg.com

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-12-20 15:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 15:53 Steve Wise [this message]
2017-12-20 16:14 ` dumping queue state Bart Van Assche
     [not found]   ` <1513786487.2603.4.camel-Sjgp3cTcYWE@public.gmane.org>
2017-12-20 16:59     ` Steve Wise
2017-12-20 16:36 ` Leon Romanovsky
     [not found]   ` <20171220163655.GW2942-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-12-20 17:00     ` Steve Wise
2017-12-20 17:11       ` Leon Romanovsky
     [not found]         ` <20171220171146.GX2942-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-12-20 17:42           ` Steve Wise
2017-12-20 18:05             ` Leon Romanovsky
     [not found]               ` <20171220180549.GY2942-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-12-20 19:01                 ` Steve Wise
2017-12-20 20:01                   ` Leon Romanovsky
     [not found]                     ` <20171220200115.GC2942-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-12-20 21:42                       ` Steve Wise
2017-12-21  5:15                         ` Leon Romanovsky
2017-12-20 19:31                 ` Steve Wise
2017-12-20 19:58                   ` 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='00a701d379aa$b098ee10$11caca30$@opengridcomputing.com' \
    --to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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