public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitrii Tcvetkov <demfloro@demfloro.ru>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block <linux-block@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Bisected GFP in bfq_bfqq_expire on v5.1-rc1
Date: Mon, 1 Apr 2019 12:22:33 +0300	[thread overview]
Message-ID: <20190401122233.3e861312@fire.localdomain> (raw)
In-Reply-To: <84B0CA50-0ED8-4171-8007-19EA43951735@linaro.org>

On Mon, 1 Apr 2019 11:01:27 +0200
Paolo Valente <paolo.valente@linaro.org> wrote:
> Ok, thank you. Could you please do a
> 
> list *(bfq_bfqq_expire+0x1f3)
> 
> for me?
> 
> Thanks,
> Paolo
> 
> > 
> > <gpf.txt><gpf-w-bfq-group-iosched.txt><config.txt>

Reading symbols from vmlinux...done.
(gdb) list *(bfq_bfqq_expire+0x1f3)
0xffffffff813d02c3 is in bfq_bfqq_expire (block/bfq-iosched.c:3390).
3385             * even in case bfqq and thus parent entities go on receiving 
3386             * service with the same budget.
3387             */
3388            entity = entity->parent;
3389            for_each_entity(entity)
3390                    entity->service = 0;
3391    }
3392
3393    /*
3394     * Budget timeout is not implemented through a dedicated timer, but

  reply	other threads:[~2019-04-01  9:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-29 13:02 Bisected GFP in bfq_bfqq_expire on v5.1-rc1 Dmitrii Tcvetkov
2019-03-29 14:10 ` Jens Axboe
2019-04-01  7:29   ` Paolo Valente
2019-04-01  8:55     ` Dmitrii Tcvetkov
2019-04-01  9:01       ` Paolo Valente
2019-04-01  9:22         ` Dmitrii Tcvetkov [this message]
2019-04-01 10:35           ` Paolo Valente
2019-04-04 19:22             ` Dmitrii Tcvetkov
2019-04-09  9:55               ` Paolo Valente
2019-04-09 16:14                 ` Dmitrii Tcvetkov

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=20190401122233.3e861312@fire.localdomain \
    --to=demfloro@demfloro.ru \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.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