public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Chris Friesen <chris.friesen@genband.com>
Cc: fuse-devel@lists.sourceforge.net,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: ionice and FUSE-based filesystems?
Date: Fri, 03 Sep 2010 20:57:24 +0200	[thread overview]
Message-ID: <4C814514.4040103@kernel.dk> (raw)
In-Reply-To: <4C800B06.90005@genband.com>

On 09/02/2010 10:37 PM, Chris Friesen wrote:
> 
> 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?

Miklos should be able to expand on what fuse does, but at least on
the write side priorities will only be carried through for non-buffered
writes with the current design (since actual write out happens out of
context of the submitting application).

-- 
Jens Axboe


  parent reply	other threads:[~2010-09-03 18:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 20:37 ionice and FUSE-based filesystems? Chris Friesen
2010-09-03 17:38 ` [fuse-devel] " Manuel Amador (Rudd-O)
2010-09-03 18:57 ` Jens Axboe [this message]
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=4C814514.4040103@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chris.friesen@genband.com \
    --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