diff options
| author | Wu Fengguang <fengguang.wu@intel.com> | 2009-04-02 16:46:06 -0400 |
|---|---|---|
| committer | Chris Mason <chris.mason@oracle.com> | 2009-04-02 16:46:06 -0400 |
| commit | d4a789474a6213d1b55b363fb1787b0abf877bba (patch) | |
| tree | cce6f1ade81778ef63921b2ed9c37b7bf2e5524d /fs/btrfs/locking.c | |
| parent | 2e966ed22c3c56227f8a7322d7b008945352e6ab (diff) | |
| download | linux-d4a789474a6213d1b55b363fb1787b0abf877bba.tar.bz2 | |
Btrfs: fix typos in comments
Signed-off-by: Chris Mason <chris.mason@oracle.com>
Diffstat (limited to 'fs/btrfs/locking.c')
| -rw-r--r-- | fs/btrfs/locking.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/fs/btrfs/locking.c b/fs/btrfs/locking.c index a5310c0f41e2..1c36e5cd8f55 100644 --- a/fs/btrfs/locking.c +++ b/fs/btrfs/locking.c @@ -60,8 +60,8 @@ void btrfs_clear_lock_blocking(struct extent_buffer *eb) /* * unfortunately, many of the places that currently set a lock to blocking - * don't end up blocking for every long, and often they don't block - * at all. For a dbench 50 run, if we don't spin one the blocking bit + * don't end up blocking for very long, and often they don't block + * at all. For a dbench 50 run, if we don't spin on the blocking bit * at all, the context switch rate can jump up to 400,000/sec or more. * * So, we're still stuck with this crummy spin on the blocking bit, |