All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: b.zolnierkie@samsung.com,
	ksummit-discuss@lists.linux-foundation.org,
	Jens Axboe <axboe@fb.com>,
	hare@suse.de, Tejun Heo <tj@kernel.org>,
	osandov@osandov.com, hch@lst.de
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Addressing long-standing high-latency problems related to I/O
Date: Fri, 16 Sep 2016 10:24:15 +0200	[thread overview]
Message-ID: <20160916082415.GA15313@kroah.com> (raw)
In-Reply-To: <E9D83DEA-B8D1-4E51-AF9C-8C67CFEDCE39@linaro.org>

On Fri, Sep 16, 2016 at 09:55:45AM +0200, Paolo Valente wrote:
> Linux systems suffers from long-standing high-latency problems, at
> system and application level, related to I/O.  For example, they
> usually suffer from poor responsiveness--or even starvation, depending
> on the workload--while, e.g., one or more files are being
> read/written/copied.  On a similar note, background workloads may
> cause audio/video playback/streaming to stutter, even with long gaps.
> A lot of test results on this problem can be found here [1] (I'm
> citing only this resource just because I'm familiar with it, but
> evidence can be found in countless technical reports, scientific
> papers, forum discussions, and so on).

<snip>

Isn't this a better topic for the Vault conference, or the storage mini
conference?

thanks,

greg k-h

  reply	other threads:[~2016-09-16  8:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16  7:55 [Ksummit-discuss] [TECH TOPIC] Addressing long-standing high-latency problems related to I/O Paolo Valente
2016-09-16  8:24 ` Greg KH [this message]
2016-09-16  8:59   ` Linus Walleij
2016-09-16  9:10     ` Bart Van Assche
2016-09-16 11:24       ` Linus Walleij
2016-09-16 11:46         ` Arnd Bergmann
2016-09-16 13:10           ` Paolo Valente
2016-09-16 13:36           ` Linus Walleij
2016-09-16 11:53         ` Bart Van Assche
2016-09-22  9:18     ` Ulf Hansson
2016-09-22 11:06       ` Linus Walleij
2016-09-16 15:15   ` James Bottomley
2016-09-16 18:48     ` Paolo Valente
2016-09-16 19:36       ` James Bottomley
2016-09-16 20:13         ` Paolo Valente
2016-09-19  8:17           ` Jan Kara
2016-09-17 10:31         ` Linus Walleij
2016-09-21 13:51         ` Grant Likely
2016-09-21 14:30 ` Bart Van Assche
2016-09-21 14:37   ` Paolo Valente

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=20160916082415.GA15313@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@fb.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=ksummit-discuss@lists.linux-foundation.org \
    --cc=osandov@osandov.com \
    --cc=paolo.valente@linaro.org \
    --cc=tj@kernel.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.