Thread (11 messages) 11 messages, 3 authors, 2012-07-17

Re: [PATCH 0/3] fs/sysv: stop using write_supers and s_dirt

From: Artem Bityutskiy <dedekind1@gmail.com>
Date: 2012-07-12 14:49:32
Also in: lkml

On Thu, 2012-07-12 at 17:37 +0300, Artem Bityutskiy wrote:
On Tue, 2012-07-03 at 16:43 +0300, Artem Bityutskiy wrote:
quoted
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

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help