Re: New data=ordered code pushed out to btrfs-unstable

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2008-07-20 at 09:46 -0400, Ric Wheeler wrote:
>            
> >>>>>> Just to kick the tires, I tried the same test that I ran last week on 
> >>>>>> ext4. Everything was going great, I decided to kill it after 6 million 
> >>>>>> files or so and restart.
> >>>>>>         
> >>>>>>             
> >>> Well, it looks like I neglected to push all the changesets, especially
> >>> the last one that made it less racey.  So, I've just done another push,
> >>> sorry.  For the fs_mark workload, it shouldn't change anything.
> >>>
> >>> This code still hasn't really survived an overnight run, hopefully this
> >>> commit will.
> >>>
> >> The test is still running, but slowly, with a (slow) stream of messages 
> >> about:

[ lock timeouts and stalls ]


Ok, I've made a few changes that should lower overall contenion on the
allocation mutex.  I'm getting better performance on a 3 million file
run, please give it a shot.

-chris


--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux