From: Chris Friesen <chris.friesen@genband.com>
To: fuse-devel@lists.sourceforge.net, axboe@kernel.dk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: ionice and FUSE-based filesystems?
Date: Thu, 02 Sep 2010 14:37:26 -0600 [thread overview]
Message-ID: <4C800B06.90005@genband.com> (raw)
I'm curious about the limits of using ionice with multiple layers of
filesystems and devices.
In particular, we have a scenario with a FUSE-based filesystem running
on top of xfs on top of LVM, on top of software RAID, on top of spinning
disks. (Something like that, anyways.) The IO scheduler is CFQ.
In the above scenario would you expect the IO nice value of the writes
done by a task to be propagated all the way down to the disk writes? Or
would they get stripped off at some point?
Thanks,
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband.com
www.genband.com
next reply other threads:[~2010-09-02 20:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 20:37 Chris Friesen [this message]
2010-09-03 17:38 ` [fuse-devel] ionice and FUSE-based filesystems? Manuel Amador (Rudd-O)
2010-09-03 18:57 ` Jens Axboe
2010-09-03 19:24 ` Chris Friesen
2010-09-03 19:25 ` Chris Friesen
2010-09-08 14:25 ` 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=4C800B06.90005@genband.com \
--to=chris.friesen@genband.com \
--cc=axboe@kernel.dk \
--cc=fuse-devel@lists.sourceforge.net \
--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