public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heinz Diehl <htd@fancy-poultry.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Bug on Kernel 3.16 r6: Sound and Buffering in Clementine with Files are Transferring to Music Directory
Date: Mon, 28 Jul 2014 11:54:42 +0200	[thread overview]
Message-ID: <20140728095442.GA4875@fancy-poultry.org> (raw)
In-Reply-To: <CAPDOMVgjLU+r82eKFA=4-v_oS+4c4fCtovcZMer5x5GAW56DSw@mail.gmail.com>

First: my email you are quoting here was sent to you directly, off-list,
because it only contains common stuff and has nothing to do with
kernel development. In other words to avoid annoying lkml people. 
In addition, I placed an "Reply-to" header pointing back to me. 
Despite, you *manually* redirected your answer to my private mail 
back to the list, thus annoying people and breaking the informational
flow of this thread.


On 27.07.2014, Nick Krause wrote: 

> I am transferring into the same directory for the music 
> I am listening to.

So you produce a lot of disk I/O by writing/reading from the same disk
at the same time, and as you encounter stalls, you take this for a
kernel bug (which clearly is not). These stalls are most probably
caused by fsync() flushing your data/buffers, which is blocking.

So moving the music data you are listening to to another disk would
make things a lot easier.

> In addition , my cpu usage when doing this is half of my older

DMA transfer is mostly done be the controller itself, and not the CPU.

Btw, EOT for me.


  parent reply	other threads:[~2014-07-28  9:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-27  3:41 Bug on Kernel 3.16 r6: Sound and Buffering in Clementine with Files are Transferring to Music Directory Nick Krause
2014-07-27  5:07 ` Matt Joras
2014-07-27  6:50   ` Mike Galbraith
2014-07-27  6:36 ` Mike Galbraith
     [not found] ` <20140727083758.GA4834@fancy-poultry.org>
2014-07-27 20:18   ` Nick Krause
2014-07-27 20:37     ` Nick Krause
2014-07-28  9:54     ` Heinz Diehl [this message]
2014-07-28 15:09       ` Nick Krause
2014-07-28 20:13         ` Heinz Diehl
2014-07-28 22:24           ` Nick Krause
2014-07-29  5:37             ` Nick Krause
2014-07-29  5:57               ` Nick Krause
     [not found]                 ` <2b1c82c0922238cbceabae6b6dc056f9@mjoras.com>
     [not found]                   ` <CAPDOMVh7DnV4r=aLbReb8KATW_6u_PVKX-CfnSQ3Q2WxpSbzMw@mail.gmail.com>
2014-07-29 17:34                     ` Nick Krause
2014-07-30  5:00                       ` Nick Krause

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=20140728095442.GA4875@fancy-poultry.org \
    --to=htd@fancy-poultry.org \
    --cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox