From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "eduval@amazon.com" <eduval@amazon.com>
Cc: "hch@lst.de" <hch@lst.de>, "osandov@fb.com" <osandov@fb.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"hare@suse.com" <hare@suse.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"ming.lei@redhat.com" <ming.lei@redhat.com>
Subject: Re: [PATCH v2 3/4] blk-mq-debugfs: Show busy requests
Date: Wed, 31 May 2017 21:45:54 +0000 [thread overview]
Message-ID: <1496267153.2608.17.camel@sandisk.com> (raw)
In-Reply-To: <20170531214327.GD7903@u40b0340c692b58f6553c.ant.amazon.com>
On Wed, 2017-05-31 at 14:43 -0700, Eduardo Valentin wrote:
> On Wed, May 31, 2017 at 02:30:49PM -0700, Bart Van Assche wrote:
> > +static void hctx_show_busy(struct request *rq, void *data, bool reserv=
ed)
> > +{
> > + const struct show_busy_params *params =3D data;
> > +
> > + if (blk_mq_map_queue(rq->q, rq->mq_ctx->cpu) =3D=3D params->hctx &&
> > + test_bit(REQ_ATOM_STARTED, &rq->atomic_flags))
> > + __blk_mq_debugfs_rq_show(params->m,
> > + list_entry_rq(&rq->queuelist));
> > +}
> > +
> > +static int hctx_busy_show(void *data, struct seq_file *m)
> > +{
> > + struct blk_mq_hw_ctx *hctx =3D data;
> > + struct show_busy_params params =3D { .m =3D m, .hctx =3D hctx };
> > +
> > + blk_mq_tagset_busy_iter(hctx->queue->tag_set, hctx_show_busy, ¶ms=
);
> > +
> > + return 0;
> > +}
>=20
> Why not making the two above one single function?
> hctx_busy_show vs. hctx_show_busy seams a bit confusing, and I could not =
see
> where they get reused in your patch set..
Hello Eduardo,
If I would open-code blk_mq_tagset_busy_iter() then I would be able to impl=
ement
the above two functions as a single function. However, blk_mq_tagset_busy_i=
ter()
expects a function pointer as third argument. That's why the above function=
ality
has been split over two functions.
Bart.=
next prev parent reply other threads:[~2017-05-31 21:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 21:30 [PATCH v2 0/4] blk-mq-debugfs patches for kernel v4.13 Bart Van Assche
2017-05-31 21:30 ` [PATCH v2 1/4] blk-mq-debugfs: Show atomic request flags Bart Van Assche
2017-06-01 2:37 ` Ming Lei
2017-05-31 21:30 ` [PATCH v2 2/4] blk-mq-debugfs: Show requeue list Bart Van Assche
2017-06-01 2:41 ` Ming Lei
2017-05-31 21:30 ` [PATCH v2 3/4] blk-mq-debugfs: Show busy requests Bart Van Assche
2017-05-31 21:43 ` Eduardo Valentin
2017-05-31 21:45 ` Bart Van Assche [this message]
2017-05-31 21:49 ` Eduardo Valentin
2017-05-31 21:54 ` Bart Van Assche
2017-05-31 23:27 ` Eduardo Valentin
2017-06-01 2:47 ` Ming Lei
2017-06-01 5:48 ` Hannes Reinecke
2017-05-31 21:30 ` [PATCH v2 4/4] blk-mq-debugfs: Add 'kick' operation Bart Van Assche
2017-06-01 2:50 ` Ming Lei
2017-06-01 5:48 ` Hannes Reinecke
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=1496267153.2608.17.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=eduval@amazon.com \
--cc=hare@suse.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=osandov@fb.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