All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: get_fs_excl/put_fs_excl/has_fs_excl
Date: Thu, 23 Apr 2009 21:21:24 +0200	[thread overview]
Message-ID: <20090423192123.GL4593@kernel.dk> (raw)
In-Reply-To: <20090423191817.GA22521@lst.de>

On Thu, Apr 23 2009, Christoph Hellwig wrote:
> Stumbled over these gems recently when investigating the
> lock_super/unlock_super removal.
> 
> These were added in commit 22e2c507c301c3dbbcf91b4948b88f78842ee6c9
> 
>         [PATCH] Update cfq io scheduler to time sliced design
> 
> which unfortunately doesn't contain any comments about it.  It seems to
> be used to allow boosting priority for some sort of central fs metadata
> updates, at least what the usage in the reiserfs journal code
> looks like that.
> 
> Do you happen to have some notes/anecdotes about it so that we can
> document it, give it saner naming and use it directly in the
> spots that need it (including inside xfs, btrfs, etc) instead of lock_super?

The intent was to add some sort of notification mechanism from the file
system to inform the IO scheduler (and others?) that this process is how
holding a file system wide resource. So if you have a low priority
process getting access to such a resource, you want to boost its
priority to avoid higher priority apps getting stuck beind it. Sort of a
poor mans priority inheritance.

It would be wonderful if you could kick this process more into gear on
the fs side...

-- 
Jens Axboe


  reply	other threads:[~2009-04-23 19:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 19:18 get_fs_excl/put_fs_excl/has_fs_excl Christoph Hellwig
2009-04-23 19:21 ` Jens Axboe [this message]
2009-04-23 21:23   ` get_fs_excl/put_fs_excl/has_fs_excl Jamie Lokier
2009-04-24  5:58     ` get_fs_excl/put_fs_excl/has_fs_excl Jens Axboe
2009-04-24 18:40   ` get_fs_excl/put_fs_excl/has_fs_excl Christoph Hellwig
2009-04-25 15:16     ` get_fs_excl/put_fs_excl/has_fs_excl Theodore Tso
2009-04-27  9:53       ` get_fs_excl/put_fs_excl/has_fs_excl Jens Axboe
2009-04-27 11:33         ` get_fs_excl/put_fs_excl/has_fs_excl Theodore Tso
2009-04-27 14:47           ` get_fs_excl/put_fs_excl/has_fs_excl Jamie Lokier
2009-04-27 16:29             ` get_fs_excl/put_fs_excl/has_fs_excl Theodore Tso
2009-04-27 17:03               ` get_fs_excl/put_fs_excl/has_fs_excl Jamie Lokier

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=20090423192123.GL4593@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.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 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.