All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "paolo.valente@linaro.org" <paolo.valente@linaro.org>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"tj@kernel.org" <tj@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [WIP PATCHSET 0/4] WIP branch for bfq-mq
Date: Mon, 13 Feb 2017 22:07:20 +0000	[thread overview]
Message-ID: <1487023626.2719.9.camel@sandisk.com> (raw)
In-Reply-To: <1A8DF6A8-C251-472A-9CE1-ACB1BCD0E9AB@linaro.org>

On Mon, 2017-02-13 at 22:07 +0100, Paolo Valente wrote:
> but what do you think about trying this fix?

Sorry but with ... the same server I used for the previous test still
didn't boot up properly. A screenshot is available at
https://goo.gl/photos/Za9QVGCNe2BJBwxVA.

> Otherwise, if you have no news or suggestions, would you be willing to
> try my micro-logging proposal https://github.com/Algodev-github/bfq-mq?

Sorry but it's not clear to me what logging mechanism you are referring
to and how to enable it? Are you perhaps referring to
CONFIG_BFQ_REDIRECT_TO_CONSOLE?

Thanks,

Bart.
Western Digital Corporation (and its subsidiaries) E-mail Confidentiality N=
otice & Disclaimer:

This e-mail and any files transmitted with it may contain confidential or l=
egally privileged information of WDC and/or its affiliates, and are intende=
d solely for the use of the individual or entity to which they are addresse=
d. If you are not the intended recipient, any disclosure, copying, distribu=
tion or any action taken or omitted to be taken in reliance on it, is prohi=
bited. If you have received this e-mail in error, please notify the sender =
immediately and delete the e-mail in its entirety from your system.

WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "paolo.valente@linaro.org" <paolo.valente@linaro.org>
Cc: "ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
	"tj@kernel.org" <tj@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"broonie@kernel.org" <broonie@kernel.org>,
	"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Subject: Re: [WIP PATCHSET 0/4] WIP branch for bfq-mq
Date: Mon, 13 Feb 2017 22:07:20 +0000	[thread overview]
Message-ID: <1487023626.2719.9.camel@sandisk.com> (raw)
In-Reply-To: <1A8DF6A8-C251-472A-9CE1-ACB1BCD0E9AB@linaro.org>

On Mon, 2017-02-13 at 22:07 +0100, Paolo Valente wrote:
> but what do you think about trying this fix?

Sorry but with ... the same server I used for the previous test still
didn't boot up properly. A screenshot is available at
https://goo.gl/photos/Za9QVGCNe2BJBwxVA.

> Otherwise, if you have no news or suggestions, would you be willing to
> try my micro-logging proposal https://github.com/Algodev-github/bfq-mq?

Sorry but it's not clear to me what logging mechanism you are referring
to and how to enable it? Are you perhaps referring to
CONFIG_BFQ_REDIRECT_TO_CONSOLE?

Thanks,

Bart.

  reply	other threads:[~2017-02-13 22:07 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-07 17:24 [WIP PATCHSET 0/4] WIP branch for bfq-mq Paolo Valente
2017-02-07 17:24 ` [WIP PATCHSET 1/4] blk-mq: pass bio to blk_mq_sched_get_rq_priv Paolo Valente
2017-02-10 16:10   ` Jens Axboe
2017-02-07 17:24 ` [WIP PATCHSET 2/4] Move thinktime from bic to bfqq Paolo Valente
2017-02-07 17:24 ` [WIP PATCHSET 3/4] Embed bfq-ioc.c and add locking on request queue Paolo Valente
2017-02-07 17:24 ` [WIP PATCHSET 4/4] Modify interface and operation to comply with blk-mq-sched Paolo Valente
2017-02-10 16:08 ` [WIP PATCHSET 0/4] WIP branch for bfq-mq Bart Van Assche
2017-02-10 16:08   ` Bart Van Assche
2017-02-10 16:49   ` Paolo Valente
2017-02-10 16:49     ` Paolo Valente
2017-02-10 16:45 ` Bart Van Assche
2017-02-10 16:45   ` Bart Van Assche
2017-02-10 16:49   ` Paolo Valente
2017-02-10 16:49     ` Paolo Valente
2017-02-10 18:13     ` Bart Van Assche
2017-02-10 18:13       ` Bart Van Assche
2017-02-10 19:49       ` Paolo Valente
2017-02-10 19:49         ` Paolo Valente
2017-02-13 21:07         ` Paolo Valente
2017-02-13 21:07           ` Paolo Valente
2017-02-13 22:07           ` Bart Van Assche [this message]
2017-02-13 22:07             ` Bart Van Assche
2017-02-13 22:38             ` Bart Van Assche
2017-02-13 22:38               ` Bart Van Assche
2017-02-22 21:29               ` Paolo Valente
2017-02-22 21:29                 ` Paolo Valente
2017-02-24 18:44                 ` Bart Van Assche
2017-02-24 18:44                   ` Bart Van Assche
2017-02-25 17:45                   ` Paolo Valente
2017-02-25 17:45                     ` Paolo Valente
2017-02-10 18:34 ` Bart Van Assche
2017-02-10 18:34   ` Bart Van Assche
2017-02-10 19:33   ` Paolo Valente
2017-02-10 19:33     ` Paolo Valente
2017-02-13 21:09 ` Paolo Valente
2017-02-13 21:09   ` Paolo Valente
2017-02-13 22:29   ` Jens Axboe

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=1487023626.2719.9.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=axboe@kernel.dk \
    --cc=broonie@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.org \
    --cc=tj@kernel.org \
    --cc=ulf.hansson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.