All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adam Manzanares <adam.manzanares@wdc.com>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: <lsf-pc@lists.linux-foundation.org>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Mark Brown <broonie@linaro.org>, <linux-block@vger.kernel.org>,
	<cyril.guyot@wdc.com>
Subject: Re: [LSF/MM ATTEND AND AGENDA TOPIC] request to attend the summit
Date: Fri, 6 Jan 2017 15:05:54 -0800	[thread overview]
Message-ID: <20170106230553.GA23927@hgst.com> (raw)
In-Reply-To: <771BC555-46A4-4AE1-BDD5-BFB4E3F065F0@linaro.org>

The 01/02/2017 19:14, Paolo Valente wrote:
> Hi,
> this is to retry to request to attend the summit.  This time I'm
> trying to propose and agenda topic too.
> 
> I would like to attend, and propose a topic, because:
> 1) the project for adding (only) the BFQ I/O scheduler to blk-mq has
> entered a quite active phase: the framework prepared by Jens seems
> mostly ready and complete, and I need just a few details to complete
> the port of BFQ.
> 2) the landing of BFQ into blk-mq might have possibly important
> consequences, in a way or the other.
> 
> So, it might be quite useful for me, and possibly for other
> developers/stakeholders interested in these changes and consequences,
> to have the opportunity to talk with each other, exactly when, or
> right after these changes happen.
> 
> In addition, a few months ago Greg KH and James Bottomley even
> suggested to postpone to this summit, or Vault, the KS discussion that
> I proposed on the unsolved latency problems for which BFQ has been
> devised.  So, my topic proposal would be exactly this:
> "Unsolved latency problems, related to I/O, in Linux: consequences on
> lsb-compliant and Android systems, solutions proposed so far, possible
> next solutions".

Hello,

We are also interested in the unsolved latency problems. In 4.10 we got 
some patches merged that deal with iopriority being passed from the 
application to device drivers that send commands to SATA HDDs. This allows an 
application to achieve better tail latencies for prioritized workloads 
when queuing is enabled at the device. 

We would like to discuss the implications of adapting this work to block-mq 
and BFQ. In addition we would like to discuss potential applications and 
devices (including device driver changes) that would benefit from having 
iopriority information.

Thanks,
Adam 

> 
> If needed, I can provide more details on this topic.
> 
> As for the expertise that I may bring, I'm somehow expert in:
> guaranteeing a good system and application responsiveness (a low lag
> in typical Android terminology), providing strong low-latency
> guarantees to video/audio playing/streaming applications, guaranteeing
> a fair share of the bandwidth, and not just the time, of I/O
> resources.
> 
> I would like to submit a talk proposal to Vault too.
> 
> Thanks,
> Paolo
> --
> To unsubscribe from this list: send the line "unsubscribe linux-block" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2017-01-06 23:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-02 18:14 [LSF/MM ATTEND AND AGENDA TOPIC] request to attend the summit Paolo Valente
2017-01-03  8:17 ` Bart Van Assche
2017-01-03  9:39   ` Paolo Valente
2017-01-03 12:00     ` Bart Van Assche
2017-01-03 17:23       ` Paolo Valente
2017-01-04  7:41         ` [Lsf-pc] " Jan Kara
2017-01-08 16:30     ` Bart Van Assche
2017-01-08 16:56       ` Paolo Valente
2017-01-10  9:55   ` Ulf Hansson
2017-01-06 23:05 ` Adam Manzanares [this message]

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=20170106230553.GA23927@hgst.com \
    --to=adam.manzanares@wdc.com \
    --cc=broonie@linaro.org \
    --cc=cyril.guyot@wdc.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-block@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=paolo.valente@linaro.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.