From: Oliver Neukum <oliver@neukum.org>
To: "Morales, Alejandra" <alejandra.morales@tum.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Doubts on IO requests in USB subsystem
Date: Mon, 09 Sep 2013 18:40:18 +0200 [thread overview]
Message-ID: <1378744818.1381.4.camel@linux-fkkt.site> (raw)
In-Reply-To: <9E3F9C2076C45D4783F09B90D5BE77CE189C61@BADWLRZ-SWMBX13.ads.mwn.de>
On Mon, 2013-09-09 at 08:20 +0000, Morales, Alejandra wrote:
> mounted and there is no application using them at the moment, so that
> I was expecting that none
> of them receive file system requests. Indeed the SATA HD does not
> receive any requests unless I
> mount or unmount it, but the USB HD receives a large number of file
> system requests and it seems
> that it never enters into an idle state. Since any application is
> using it I think these requests may
> come from the USB subsystem. Am I right? If so, how could I determine
> whether a request comes
> from the USB subsystem or it is a file system request that actually
> moves blocks?
Your prime suspect is the detection of medium change which was
moved into the kernel in 3.2 or so. It can be disabled by sysfs.
Generally the notion that a certain task originates a read or write
on a block device is iffy. Read-ahead and shared data structures
make it impossible to accurately tell.
USB storage devices are notorious for setting the removable bit
even if they have no removable medium.
Regards
Oliver
next prev parent reply other threads:[~2013-09-09 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 8:20 Doubts on IO requests in USB subsystem Morales, Alejandra
2013-09-09 16:40 ` Oliver Neukum [this message]
2013-09-16 10:33 ` Morales, Alejandra
2013-09-16 11:06 ` Oliver Neukum
2013-11-06 11:51 ` Morales, Alejandra
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=1378744818.1381.4.camel@linux-fkkt.site \
--to=oliver@neukum.org \
--cc=alejandra.morales@tum.de \
--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