mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Al Viro <viro@ZenIV.linux.org.uk>,
	Linux Kernel Maling List <linux-kernel@vger.kernel.org>,
	Linux FS Maling List <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 0/3] fs/sysv: stop using write_supers and s_dirt
Date: Thu, 12 Jul 2012 17:49:32 +0300	[thread overview]
Message-ID: <1342104572.18274.108.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1342103878.18274.98.camel@sauron.fi.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

On Thu, 2012-07-12 at 17:37 +0300, Artem Bityutskiy wrote:
> On Tue, 2012-07-03 at 16:43 +0300, Artem Bityutskiy wrote:
> > This patch-set makes sysv file-system stop using the VFS '->write_supers()'
> > call-back and the '->s_dirt' superblock field because I plan to remove them
> > once all users are gone.
> 
> Hi Andrew,
> 
> would you please pick this patch-set as well? I also sent you an update
> for hfs and hfsplus file-systems today - found a bug while doing some
> more testing. Also, I sent UFS changes today, very similar. Most
> probably no one will reply and I hope you would pick them as well.

Just to let you know about the overall picture. Pending FSes (no one
picked them) are:

1. ext4 - Ted is still being busy.
2. sysv, ufs - I hope you'd pick

After this we will be able to kill sync_supers() completely and get rid
of another source of regular wake-ups in the kernel. And interestingly,
it will be the final end of pdflush - at old times it woke up
periodically and flushed everything (forked itself as well). Then Jens
cut off the data write-back part and put it to per-block device bdi
threads. They originally also waked-up every 5 seconds, but I fixed this
in v2.6.36 (6467716) and they stopped misbehaving. Jens transformed the
superblock write-out part of pdflush 'sync_supers()', and I could not
kill it because I did not have enough time and Al's request to change
all users sounded unrealistic to me. But now I hope to actually finish
this.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-12 14:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 13:43 Artem Bityutskiy
2012-07-03 13:43 ` [PATCH 1/3] fs/sysv: remove useless write_super call Artem Bityutskiy
2012-07-03 13:43 ` [PATCH 2/3] fs/sysv: remove another " Artem Bityutskiy
2012-07-03 13:43 ` [PATCH 3/3] fs/sysv: stop using write_super and s_dirt Artem Bityutskiy
2012-07-03 14:13   ` Alan Cox
2012-07-03 14:44     ` Artem Bityutskiy
2012-07-12 14:37 ` [PATCH 0/3] fs/sysv: stop using write_supers " Artem Bityutskiy
2012-07-12 14:49   ` Artem Bityutskiy [this message]
2012-07-13 21:42   ` Andrew Morton
2012-07-14  4:04     ` Artem Bityutskiy
2012-07-17 15:13     ` Artem Bityutskiy

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=1342104572.18274.108.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ZenIV.linux.org.uk \
    /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

Powered by JetHome