On Wed, 2007-10-17 at 11:57 -0600, Eric W. Biederman wrote:
Christian Borntraeger [EMAIL PROTECTED] writes:
Eric,
Am Dienstag, 16. Oktober 2007 schrieb Christian Borntraeger:
Am Dienstag, 16. Oktober 2007 schrieb Eric W. Biederman:
fs/buffer.c |3 +++
1 files changed, 3
On Wed, 2007-10-17 at 14:29 -0600, Eric W. Biederman wrote:
Chris Mason [EMAIL PROTECTED] writes:
In this case, the commit block isn't allowed to be dirty before reiserfs
decides it is safe to write it. The journal code expects it is the only
spot in the kernel setting buffer heads dirty
On Wed, 2007-10-17 at 15:30 -0600, Eric W. Biederman wrote:
Chris Mason [EMAIL PROTECTED] writes:
Thinking about it. I don't believe anyone has ever intentionally built
a filesystem tool that depends on being able to modify a file systems
metadata buffer heads while the filesystem
On Wed, 2007-10-17 at 17:28 -0600, Eric W. Biederman wrote:
Chris Mason [EMAIL PROTECTED] writes:
So, the problem is using the Dirty bit to indicate pinned. You're
completely right that our current setup of buffer heads and pages and
filesystpem metadata is complex and difficult
On Sun, 21 Oct 2007 12:39:30 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
Nick Piggin [EMAIL PROTECTED] writes:
On Sunday 21 October 2007 18:23, Eric W. Biederman wrote:
Christian Borntraeger [EMAIL PROTECTED] writes:
Let me put it another way. Looking at /proc/slabinfo I can
On Tue, 23 Oct 2007 19:56:20 +0800
Fengguang Wu [EMAIL PROTECTED] wrote:
On Tue, Oct 23, 2007 at 12:07:07PM +0200, Peter Zijlstra wrote:
[ adding reiserfs devs to the CC ]
Thank you.
This fix is kind of crude - even when it fixed Maxim's problem, and
survived my stress testing of a lot
Hello everyone,
We are organizing another filesystem and storage workshop in San Jose
next Feb 25 and 26. You can find some great writeups of last year's
conference on LWN:
http://lwn.net/Articles/226351/
This year we're trying to concentrate on more problem solving sessions,
short term
On Sunday 10 February 2008, David Miller wrote:
From: Chris Mason [EMAIL PROTECTED]
Date: Wed, 6 Feb 2008 12:00:13 -0500
This function never returns an error, so the simplest fix was to
return the hash value which avoids all of the issues. In attempting
other schemes to fix this, I found
On Tuesday 12 February 2008, David Miller wrote:
From: Chris Mason [EMAIL PROTECTED]
Date: Wed, 6 Feb 2008 12:00:13 -0500
So, here's v0.12.
Any page size larger than 4K will not work with btrfs. All of the
extent stuff assumes that PAGE_SIZE = sectorsize.
Yeah, there is definitely clean
On Tuesday 12 February 2008, Jan Engelhardt wrote:
On Feb 12 2008 09:08, Chris Mason wrote:
So, if Btrfs starts zeroing at 1k, will that be acceptable for you?
Something looks wrong here. Why would btrfs need to zero at all?
Superblock at 0, and done. Just like xfs.
(Yes, I had xfs
On Tuesday 12 February 2008, Jan Engelhardt wrote:
On Feb 12 2008 08:49, Chris Mason wrote:
This is a real issue on sparc where the default sun disk labels
created use an initial partition where block zero aliases the disk
label. It took me a few iterations before I figured out why
On Tuesday 12 February 2008, Jan Engelhardt wrote:
On Feb 12 2008 09:35, Chris Mason wrote:
and slap the bootloader into MBR, just like on x86.
Or I am missing something..
It was a request from hpa, and he clearly had something in mind. He
kindly offered to review the disk format
On Tuesday 12 February 2008, David Miller wrote:
From: Chris Mason [EMAIL PROTECTED]
Date: Mon, 11 Feb 2008 08:42:20 -0500
The kernel is actually worse, because the set/get macros are more
complex. Some live in ctree.h like in the progs, but the nasty ones live
in struct-funcs.c
On Mon, Oct 08, 2012 at 07:26:15AM -0600, Wang Sheng-Hui wrote:
In csum_dirty_buffer, we first get eb from page-private.
Then we check if the page is the first page of eb. Later
we check it again. Remove the repeated check here.
You had the right idea here, two checks and one has a warning, so
inode ref iteration (+138/-37)
btrfs: extended inode refs (+710/-79)
Wei Yongjun (2) commits (+3/-6):
Btrfs: fix possible memory leak in scrub_setup_recheck_block() (+1/-0)
Btrfs: using for_each_set_bit_from to simplify the code (+2/-6)
Chris Mason (2) commits (+38/-16):
Btrfs: fix
Hi Linus,
My for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Has our series of fixes for the next rc. The biggest batch is from Jan
Schmidt, fixing up some problems in our subvolume quota code and fixing
btrfs send/receive to work with the new
Hello everyone,
Since doing the initial Btrfs benchmarks, I've made my blktrace graphing
utility a little more generic and tossed it out on oss.oracle.com.
This new version can easily graph two different runs, and has a few
other tweaks that make the graphs look nicer.
Docs, examples and other
On Tue, 10 Jul 2007 17:03:26 -0400
Chris Mason [EMAIL PROTECTED] wrote:
This patch aims to demonstrate one way to replace buffer heads with a
few extent trees. Buffer heads provide a few different features:
1) Mapping of logical file offset to blocks on disk
2) Recording state (dirty
Core Extentmap implementation
diff -r 126111346f94 -r 53cabea328f7 fs/Makefile
--- a/fs/Makefile Mon Jul 09 10:53:57 2007 -0400
+++ b/fs/Makefile Tue Jul 24 15:40:27 2007 -0400
@@ -11,7 +11,7 @@ obj-y := open.o read_write.o file_table.
attr.o bad_inode.o file.o
mount -o extentmap to use the new stuff
diff -r 126111346f94 -r 53cabea328f7 fs/ext2/ext2.h
--- a/fs/ext2/ext2.hMon Jul 09 10:53:57 2007 -0400
+++ b/fs/ext2/ext2.hTue Jul 24 15:40:27 2007 -0400
@@ -1,5 +1,6 @@
#include linux/fs.h
#include linux/ext2_fs.h
+#include linux/extent_map.h
On Tue, 24 Jul 2007 23:25:43 +0200
Peter Zijlstra [EMAIL PROTECTED] wrote:
On Tue, 2007-07-24 at 16:13 -0400, Trond Myklebust wrote:
On Tue, 2007-07-24 at 16:00 -0400, Chris Mason wrote:
On Tue, 10 Jul 2007 17:03:26 -0400
Chris Mason [EMAIL PROTECTED] wrote:
This patch aims
On Wed, 25 Jul 2007 04:32:17 +0200
Nick Piggin [EMAIL PROTECTED] wrote:
On Tue, Jul 24, 2007 at 07:25:09PM -0400, Chris Mason wrote:
On Tue, 24 Jul 2007 23:25:43 +0200
Peter Zijlstra [EMAIL PROTECTED] wrote:
The tree is a critical part of the patch, but it is also the
easiest to rip
On Thu, 26 Jul 2007 03:37:28 +0200
Nick Piggin [EMAIL PROTECTED] wrote:
One advantage to the state tree is that it separates the state from
the memory being described, allowing a simple kmap style interface
that covers subpages, highmem and superpages.
I suppose so, although we should
On Thu, 26 Jul 2007 04:36:39 +0200
Nick Piggin [EMAIL PROTECTED] wrote:
[ are state trees a good idea? ]
One thing it gains us is finding the start of the cluster. Even if
called by kswapd, the state tree allows writepage to find the start
of the cluster and send down a big bio (provided
Hello everyone,
I've tossed out seekwatcher v0.3. The major changes are using rolling
averages to smooth out the seek and throughput graphs, and it can
generate mpgs of the IO done by a given trace.
Here's a sample of the smoother graphs (creating 20 kernel trees):
On Wed, 22 Aug 2007 09:18:41 +0800
Fengguang Wu [EMAIL PROTECTED] wrote:
On Tue, Aug 21, 2007 at 08:23:14PM -0400, Chris Mason wrote:
On Sun, 12 Aug 2007 17:11:20 +0800
Fengguang Wu [EMAIL PROTECTED] wrote:
Andrew and Ken,
Here are some more experiments on the writeback stuff
On Thu, 23 Aug 2007 12:47:23 +1000
David Chinner [EMAIL PROTECTED] wrote:
On Wed, Aug 22, 2007 at 08:42:01AM -0400, Chris Mason wrote:
I think we should assume a full scan of s_dirty is impossible in the
presence of concurrent writers. We want to be able to pick a start
time (right now
On Fri, 24 Aug 2007 21:24:58 +0800
Fengguang Wu [EMAIL PROTECTED] wrote:
2) s_dirty and s_io both become radix trees. s_dirty is indexed by
a sequence number that corresponds to age. It is treated as a big
circular indexed list that can wrap around over time. Radix tree
tags are used
On Mon, 27 Aug 2007 05:03:36 -0700
Arjan van de Ven [EMAIL PROTECTED] wrote:
On Mon, 27 Aug 2007 19:21:52 +0800
Because it does the work in small batches of 10 inodes, when the
system has =10 dirty inodes, its behavior will reduce to:
- do a full sweep *at once* on every 25s
Which
:23:14PM -0400, Chris Mason wrote:
Notes:
(1) I'm not sure inode number is correlated to disk location in
filesystems other than ext2/3/4. Or parent dir?
The correspond to the exact location on disk on XFS. But, XFS has
it's own inode clustering (see xfs_iflush
On Wed, 29 Aug 2007 02:33:08 +1000
David Chinner [EMAIL PROTECTED] wrote:
On Tue, Aug 28, 2007 at 11:08:20AM -0400, Chris Mason wrote:
I wonder if XFS can benefit any more from the general writeback
clustering. How large would be a typical XFS cluster?
Depends on inode size
On Sun, 12 Aug 2007 17:11:20 +0800
Fengguang Wu [EMAIL PROTECTED] wrote:
Andrew and Ken,
Here are some more experiments on the writeback stuff.
Comments are highly welcome~
I've been doing benchmarks lately to try and trigger fragmentation, and
one of them is a simulation of make -j N. It
On Sun, 5 Aug 2007 11:00:29 -0400
Theodore Tso [EMAIL PROTECTED] wrote:
On Sun, Aug 05, 2007 at 02:26:53AM +0200, Andi Kleen wrote:
I always thought the right solution would be to just sync atime only
very very lazily. This means if a inode is only dirty because of an
atime update put it
Hello everyone,
I'm stealing the cc list and reviving and old thread because I've
finally got some numbers to go along with the Btrfs variable blocksize
feature. The basic idea is to create a read/write interface to
map a range of bytes on the address space, and use it in Btrfs for all
metadata
On Tue, 2007-10-16 at 12:36 +1000, David Chinner wrote:
On Mon, Oct 15, 2007 at 08:22:31PM -0400, Chris Mason wrote:
Hello everyone,
I'm stealing the cc list and reviving and old thread because I've
finally got some numbers to go along with the Btrfs variable blocksize
feature
On Monday 11 April 2005 03:38, Ingo Molnar wrote:
* Linus Torvalds [EMAIL PROTECTED] wrote:
So anything that got modified in just one tree obviously merges to
that version. Any file that got modified in two trees will end up just
being passed to the merge program. See man merge and man
On Monday 11 April 2005 08:51, Chris Mason wrote:
rej -M skips the merge program, so rej -a -M will give you something like
this:
coffee:/local/linux.p # rej -a -M drivers/ide/ide.c.rej
drivers/ide/ide.c: 1 matched, 0 conflicts remain
But I would want to go over the bit
On Tuesday 12 July 2005 20:27, Rob Mueller wrote:
We're also applying the attached patch. There's a bug in reiserfs that
gets tickled by our huge MMAP usage (it's amazing what really busy
Cyrus daemons can do to a server, ouch). It's fixed in generic_write,
so we take the few percent
On Tuesday 12 July 2005 20:42, Chris Mason wrote:
Sounds like a different issue. The patch Bron included before fixes (or
at least reduces to the point where it fixes it for us) a problem where
processes get stuck in D state and are unkillable. A reboot is required
to remove them
On Tuesday 12 July 2005 20:50, Rob Mueller wrote:
Are you saying that if you mount with noatime *and* use your new patch it
will fix the problem?
What about the 2 threads linked to. Did those end up getting anywhere?
Sorry for the confusion, you're hitting the other mmap_sem - transaction
On Friday 01 July 2005 03:56, Suparna Bhattacharya wrote:
Has anyone else noticed major throughput regressions for random
reads/writes with aio-stress in 2.6.12 ?
Or have there been any other FS/IO regressions lately ?
On one test system I see a degradation from around 17+ MB/s to 11MB/s
for
On Friday, July 20, 2001 10:50:57 AM +0200 Trond Myklebust
[EMAIL PROTECTED] wrote:
== Hans Reiser [EMAIL PROTECTED] writes:
The current code does rely on hidden knowledge of the filesytem
on the server, and refuses to operate with any FS that does not
describe a
Hello everyone,
This patch makes reiserfs O_SYNC and fsync faster by only
committing the last transcation a file/dir was included in,
instead of forcing a commit on the current transaction.
More speedups are still possible, this patch is fairly conservative.
It is based on 2.4.7-pre6 + the
On Tuesday, January 29, 2002 01:46:43 PM +0300 Hans Reiser [EMAIL PROTECTED] wrote:
Alexander Viro wrote:
On Tue, 29 Jan 2002, Hans Reiser wrote:
This fails to recover an object (e.g. dcache entry) which is used once,
and then spends a year in cache on the same page as an object
On Fri, Jul 13, 2012 at 04:26:26AM -0600, Thomas Gleixner wrote:
On Fri, 13 Jul 2012, Mike Galbraith wrote:
On Fri, 2012-07-13 at 11:52 +0200, Thomas Gleixner wrote:
On Fri, 13 Jul 2012, Mike Galbraith wrote:
On Thu, 2012-07-12 at 15:31 +0200, Thomas Gleixner wrote:
Bingo, that
On Wed, Jul 11, 2012 at 11:47:40PM -0600, Mike Galbraith wrote:
Greetings,
[ deadlocks with btrfs and the recent RT kernels ]
I talked with Thomas about this and I think the problem is the
single-reader nature of the RW rwlocks. The lockdep report below
mentions that btrfs is calling:
[
On Sat, Jul 14, 2012 at 04:14:43AM -0600, Mike Galbraith wrote:
On Fri, 2012-07-13 at 08:50 -0400, Chris Mason wrote:
On Wed, Jul 11, 2012 at 11:47:40PM -0600, Mike Galbraith wrote:
Greetings,
[ deadlocks with btrfs and the recent RT kernels ]
I talked with Thomas about this and I
On Mon, Jul 16, 2012 at 04:55:44AM -0600, Mike Galbraith wrote:
On Sat, 2012-07-14 at 12:14 +0200, Mike Galbraith wrote:
On Fri, 2012-07-13 at 08:50 -0400, Chris Mason wrote:
On Wed, Jul 11, 2012 at 11:47:40PM -0600, Mike Galbraith wrote:
Greetings,
[ deadlocks with btrfs
On Mon, Jul 16, 2012 at 10:26:08AM -0600, Mike Galbraith wrote:
On Mon, 2012-07-16 at 12:02 -0400, Steven Rostedt wrote:
On Mon, 2012-07-16 at 04:02 +0200, Mike Galbraith wrote:
Great, thanks! I got stuck in bug land on Friday. You mentioned
performance problems earlier on
Quoting Tejun Heo (2013-04-19 01:57:54)
Ewweehh
No wonder this thing crashes. Chris, can't the original bio carry
bbio in bi_private and let end_bio_extent_readpage() free the bbio
instead of abusing bi_bdev like this?
Yes, we can definitely carry bbio up higher
Quoting Jens Axboe (2013-04-19 09:32:50)
No wonder this thing crashes. Chris, can't the original bio carry
bbio in bi_private and let end_bio_extent_readpage() free the bbio
instead of abusing bi_bdev like this?
Ugh, wtf.
Chris, time for a swim in the bay :-)
Yeah, I can't really
Hi Linus
My for-linus branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Has a recent fix from Josef for our tree log replay code. It fixes
problems where the inode counter for the number of bytes in the file
wasn't getting updated properly during fsync
(+5/-3):
Btrfs: fix wrong return value of btrfs_lookup_csum() (+3/-1)
Btrfs: fix wrong reservation of csums (+2/-2)
Chris Mason (1) commits (+49/-0):
Btrfs: fix race between mmap writes and compression
Liu Bo (1) commits (+1/-1):
Btrfs: update to use fs_state bit
Tsutomu Itoh (1
Hi Linus,
My for-linus branch has some btrfs fixes:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Eric's rcu barrier patch fixes a long standing problem with our unmount
code hanging on to devices in workqueue helpers. Liu Bo nailed down a
difficult assertion
reloc roots (+2/-0)
Btrfs: avoid deadlock on transaction waiting list (+7/-0)
Btrfs: free all recorded tree blocks on error (+6/-3)
Btrfs: do not BUG_ON on aborted situation (+12/-3)
Btrfs: do not BUG_ON in prepare_to_reloc (+9/-1)
Chris Mason (2) commits (+96/-63):
Btrfs
On Sat, Mar 02, 2013 at 05:45:41PM -0700, Linus Torvalds wrote:
On Sat, Mar 2, 2013 at 7:15 AM, Chris Mason chris.ma...@fusionio.com wrote:
Our set of btrfs features, fixes and cleanups are in my for-linus
branch:
I *really* wish that big pull requests like this would come in earlier
On Sun, Mar 03, 2013 at 04:44:41AM -0700, Geert Uytterhoeven wrote:
tilegx_defconfig:
fs/btrfs/raid56.c: In function 'btrfs_alloc_stripe_hash_table':
fs/btrfs/raid56.c:206:3: error: implicit declaration of function 'vzalloc'
[-Werror=implicit-function-declaration]
fs/btrfs/raid56.c:206:9:
Hi Linus,
Geert and James both sent this one in, sorry guys.
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
Geert Uytterhoeven (1) commits (+1/-0):
btrfs/raid56: Add missing #include linux/vmalloc.h
Total: (1) commits (+1/-0)
fs/btrfs/raid56.c | 1 +
1 file
On Thu, Mar 07, 2013 at 01:45:33AM -0700, Peter Zijlstra wrote:
On Tue, 2013-03-05 at 15:53 -0500, Rik van Riel wrote:
Indeed. Though how well my patches will work with Oracle will
depend a lot on what kind of semctl syscalls they are doing.
Does Oracle typically do one semop per
On Thu, Mar 07, 2013 at 08:54:55AM -0700, Dave Kleikamp wrote:
On 03/07/2013 06:55 AM, Chris Mason wrote:
On Thu, Mar 07, 2013 at 01:45:33AM -0700, Peter Zijlstra wrote:
On Tue, 2013-03-05 at 15:53 -0500, Rik van Riel wrote:
Indeed. Though how well my patches will work with Oracle
On Wed, Nov 28, 2012 at 11:16:21PM -0700, Linus Torvalds wrote:
On Wed, Nov 28, 2012 at 6:58 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
But the fact that the code wants to do things like
block = (sector_t)page-index (PAGE_CACHE_SHIFT - bbits);
seriously seems to
On Thu, Nov 29, 2012 at 07:12:49AM -0700, Chris Mason wrote:
On Wed, Nov 28, 2012 at 11:16:21PM -0700, Linus Torvalds wrote:
On Wed, Nov 28, 2012 at 6:58 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
But the fact that the code wants to do things like
block
On Thu, Nov 29, 2012 at 10:26:56AM -0700, Linus Torvalds wrote:
On Thu, Nov 29, 2012 at 6:12 AM, Chris Mason chris.ma...@fusionio.com wrote:
Jumping in based on Linus original patch, which is doing something like
this:
set_blocksize() {
block new calls to writepage, prepare
On Thu, Nov 29, 2012 at 12:02:17PM -0700, Linus Torvalds wrote:
On Thu, Nov 29, 2012 at 9:19 AM, Linus Torvalds
torva...@linux-foundation.org wrote:
I think I'll apply this for 3.7 (since it's too late to do anything
fancier), and then for 3.8 I will rip out all the locking entirely,
On Thu, Nov 29, 2012 at 12:26:06PM -0700, Linus Torvalds wrote:
On Thu, Nov 29, 2012 at 11:15 AM, Chris Mason chris.ma...@fusionio.com
wrote:
The fs/buffer.c part makes sense during a quick read. But
fs/direct-io.c plays with i_blkbits too. The semaphore was fixing real
bugs
On Thu, Nov 29, 2012 at 01:52:22PM -0700, Linus Torvalds wrote:
On Thu, Nov 29, 2012 at 11:48 AM, Chris Mason chris.ma...@fusionio.com
wrote:
It was all a trick to get you to say the AIO code was sane.
It's only sane compared to the DIO code.
That said, I hate AIO much less these days
On Thu, Nov 29, 2012 at 03:36:38PM -0700, Linus Torvalds wrote:
On Thu, Nov 29, 2012 at 2:16 PM, Linus Torvalds
torva...@linux-foundation.org wrote:
But you're right. The direct-IO code really *is* violating that, and
knows that get_block() ends up being defined in i_blkbits regardless
On Thu, Nov 29, 2012 at 07:13:02PM -0700, Linus Torvalds wrote:
On Thu, Nov 29, 2012 at 5:16 PM, Chris Mason chris.ma...@fusionio.com wrote:
I searched through filemap.c for the magic i_size check that would let
us get away with ignoring i_blkbits in get_blocks, but its just
On Thu, Nov 29, 2012 at 07:49:10PM -0700, Dave Chinner wrote:
On Thu, Nov 29, 2012 at 02:16:50PM -0800, Linus Torvalds wrote:
On Thu, Nov 29, 2012 at 1:29 PM, Chris Mason chris.ma...@fusionio.com
wrote:
Just reading the new blkdev_get_blocks, it looks like we're mixing
shifts
in btrfs_file_aio_write() (+2/-1)
Jan Schmidt (1) commits (+10/-12):
Btrfs: fix EDQUOT handling in btrfs_delalloc_reserve_metadata
Liu Bo (1) commits (+38/-9):
Btrfs: fix race between snapshot deletion and getting inode
Chris Mason (1) commits (+4/-1):
Btrfs: move d_instantiate outside
Hi Arnd,
First things first, nospace_cache is a safe thing to use. It is slow
because it's finding free extents, but it's just a cache and always safe
to discard. With your other errors, I'd just mount it readonly
and then you won't waste time on atime updates.
I'll take a look at the BUG you
varargs in __btrfs_std_error (+7/-7)
btrfs: list_entry can't return NULL (+0/-2)
Chris Mason (7) commits (+561/-30):
Btrfs: reduce CPU contention while waiting for delayed extent operations
(+70/-5)
Btrfs: remove conflicting check for minimum number of devices in raid56
(+0/-8)
Btrfs
On Tue, Jan 22, 2013 at 05:48:33PM -0700, Chris Mason wrote:
Hi Linus,
My for-linus branch has our batch of btrfs fixes:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
We've been hammering away at a crc corruption as well, which I was
really hoping to get
Hi Linus,
My for-linus branch has our batch of btrfs fixes:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
It turns out that we had two crc bugs when running fsx-linux in a
loop. Many thanks to Josef, Miao Xie, and Dave Sterba for nailing it
all down. Miao also
Hi Linus,
My for-linus branch has our batch of btrfs fixes:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
We've been hammering away at a crc corruption as well, which I was
really hoping to get into this pull. It isn't nailed down yet, but we
were finally able
On Tue, Jan 22, 2013 at 06:28:21PM -0700, Liu Bo wrote:
On Tue, Jan 22, 2013 at 07:48:33PM -0500, Chris Mason wrote:
Hi Linus,
My for-linus branch has our batch of btrfs fixes:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
for-linus
We've been hammering
Hi Dan,
I'm doing some benchmarking on MD raid5/6 on 4 fusionio cards in an HP
DL380p. I'm doing 128K randomw writes on a 4 drive raid6 with a 64K
stripe size per drive. I have 4 fio processes sending down the aio/dio,
and a high queue depth (8192).
When I bump up the MD raid stripe cache
[ Sorry resend with the right address for Dan ]
Hi Dan,
I'm doing some benchmarking on MD raid5/6 on 4 fusionio cards in an HP
DL380p. I'm doing 128K randomw writes on a 4 drive raid6 with a 64K
stripe size per drive. I have 4 fio processes sending down the aio/dio,
and a high queue depth
On Thu, Jan 17, 2013 at 07:53:18PM -0700, Dan Williams wrote:
On Thu, Jan 17, 2013 at 6:38 AM, Chris Mason chris.ma...@fusionio.com wrote:
[ Sorry resend with the right address for Dan ]
Hi Dan,
I'm doing some benchmarking on MD raid5/6 on 4 fusionio cards in an HP
DL380p. I'm doing
Hi Linus,
If you're doing another RC, please grab these two. Otherwise I'll send
them off to -stable.
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git for-linus
This fixes a long standing problem where the btrfs scan ioctl was racing
with mkfs.btrfs and dropping dirty pages
On Fri, Jan 12, 2007 at 10:06:22AM -0800, Linus Torvalds wrote:
looking at the splice(2) api it seems like it'll be difficult to implement
O_DIRECT pread/pwrite from userland using splice... so there'd need to be
some help there.
You'd use vmsplice() to put the write buffers into
On Thu, Nov 30, 2006 at 10:16:53PM -0800, Chen, Kenneth W wrote:
Zach Brown wrote on Thursday, November 30, 2006 1:45 PM
At that time, a patch was written for raw device to demonstrate that
large performance head room is achievable (at ~20% speedup for micro-
benchmark and ~2% for db
.
Chris Mason (1):
Revert Btrfs: fix some error codes in btrfs_qgroup_inherit()
fs/btrfs/qgroup.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More
btrfs_compare_trees function (+440/-0)
Btrfs: make iref_to_path non static (+9/-5)
Chris Mason (5) commits (+22/-9):
Btrfs: call the ordered free operation without any locks held (+8/-1)
Btrfs: don't wait around for new log writers on an SSD (+2/-1)
Btrfs: add a barrier before
: fix race in run_clustered_refs (+17/-0)
Chris Mason (1) commits (+3/-0):
Btrfs: don't run __tree_mod_log_free_eb on leaves
Fengguang Wu (1) commits (+3/-2):
btrfs: fix second lock in btrfs_delete_delayed_items()
Miao Xie (1) commits (+1/-0):
Btrfs: fix wrong mtime and ctime when
: fix race in run_clustered_refs (+17/-0)
Chris Mason (1) commits (+3/-0):
Btrfs: don't run __tree_mod_log_free_eb on leaves
Fengguang Wu (1) commits (+3/-2):
btrfs: fix second lock in btrfs_delete_delayed_items()
Miao Xie (1) commits (+1/-0):
Btrfs: fix wrong mtime and ctime when
/-36):
Btrfs: fix a misplaced address operator in a condition (+1/-1)
Btrfs: remove superblock writing after fatal error (+5/-33)
Btrfs: fix that error value is changed by mistake (+2/-2)
Chris Mason (2) commits (+40/-15):
Btrfs: fix btrfs send for inline items and compression (+37
Hi Linus,
Please pull my for-linus-3.6 branch:
git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git
for-linus-3.6
It fixes a merging error in rc1. The calls to mnt_want_write should
have been removed.
Alexander Block (1):
Btrfs: remove mnt_want_write call in
On Mon, Aug 20, 2012 at 07:55:59PM -0600, Linus Torvalds wrote:
On Mon, Aug 20, 2012 at 6:53 PM, Chris Samuel ch...@csamuel.org wrote:
This pull request with a whole heap of btrfs fixes (46 commits) appears
not to have been merged yet, does anyone know if it was rejected or just
missed ?
Hello everyone,
I wasn't planning on releasing v0.12 yet, and it was supposed to have some
initial support for multiple devices. But, I have made a number of
performance fixes and small bug fixes, and I wanted to get them out there
before the (destabilizing) work on multiple-devices took
On Wednesday 30 January 2008, Al Boldi wrote:
Jan Kara wrote:
Chris Snook wrote:
Al Boldi wrote:
This RFC proposes to introduce a tunable which allows to disable
fsync and changes ordered into writeback writeout on a per-process
basis like this:
echo 1
On Thursday 31 January 2008, Jan Kara wrote:
On Thu 31-01-08 11:56:01, Chris Mason wrote:
On Thursday 31 January 2008, Al Boldi wrote:
Andreas Dilger wrote:
On Wednesday 30 January 2008, Al Boldi wrote:
And, a quick test of successive 1sec delayed syncs shows no hangs
until
On Thursday 31 January 2008, Al Boldi wrote:
Andreas Dilger wrote:
On Wednesday 30 January 2008, Al Boldi wrote:
And, a quick test of successive 1sec delayed syncs shows no hangs until
about 1 minute (~180mb) of db-writeout activity, when the sync abruptly
hangs for minutes on end, and
On Tue, 15 Jan 2008 11:07:40 +0100
Jens Axboe [EMAIL PROTECTED] wrote:
I split and merged the patch into five bits (added ext3 support),
so perhaps that would be easier for people to read/review.
Attached and also exist in the loop-extent_map branch here:
Thanks!
Hello everyone,
Btrfs v0.10 is now available for download from:
http://oss.oracle.com/projects/btrfs/
Btrfs is still in an early alpha state, and the disk format is not finalized.
v0.10 introduces a new disk format, and is not compatible with v0.9.
The core of this release is explicit back
On Tue, 15 Jan 2008 20:24:27 -0500
Daniel Phillips [EMAIL PROTECTED] wrote:
On Jan 15, 2008 7:15 PM, Alan Cox [EMAIL PROTECTED] wrote:
Writeback cache on disk in iteself is not bad, it only gets bad
if the disk is not engineered to save all its dirty cache on
power loss, using the disk
On Tuesday 15 January 2008, Chris Mason wrote:
Hello everyone,
Btrfs v0.10 is now available for download from:
http://oss.oracle.com/projects/btrfs/
Well, it turns out this release had a few small problems:
* data=ordered deadlock on older kernels (including 2.6.23)
* Compile problems when
On Thursday 17 January 2008, Daniel Phillips wrote:
On Jan 17, 2008 1:25 PM, Chris mason [EMAIL PROTECTED] wrote:
So, I've put v0.11 out there. It fixes those two problems and will also
compile on older (2.6.18) enterprise kernels.
v0.11 does not have any disk format changes.
Hi Chris
On Tuesday 22 January 2008, Al Boldi wrote:
Ingo Molnar wrote:
* Oliver Pinter (Pintér Olivér) [EMAIL PROTECTED] wrote:
and then please update to CFS-v24.1
http://people.redhat.com/~mingo/cfs-scheduler/sched-cfs-v2.6.22.15-v24.
1 .patch
Yes with CFSv20.4, as in the log.
On Tuesday 22 January 2008, Al Boldi wrote:
Chris Mason wrote:
Running fsync in data=ordered means that all of the dirty blocks on the
FS will get written before fsync returns.
Hm, that's strange, I expected this kind of behaviour from data=journal.
data=writeback should return immediatly
201 - 300 of 1532 matches
Mail list logo
