15 Sep, 2009
1 commit
-
Convert the journal head integer into the head name when printing
debugging information.Signed-off-by: Artem Bityutskiy
05 Jul, 2009
6 commits
-
Signed-off-by: Adrian Hunter
-
Signed-off-by: Artem Bityutskiy
-
This patch cleans up write-buffer timeout initialization and
sets it to 3-5 interval.Signed-off-by: Artem Bityutskiy
-
This patch adds the following minor optimization:
1. If write-buffer does not use the timer, indicate it with the
wbuf->no_timer variable, instead of using the wbuf->softlimit
variable. This is better because wbuf->softlimit is of ktime_t
type, and the ktime_to_ns function contains 64-bit multiplication.2. Do not call the 'hrtimer_cancel()' function for write-buffers
which do not use timers.3. Do not cancel the timer in 'ubifs_put_super()' because the
synchronization function does this.This patch also removes a confusing comment.
Signed-off-by: Artem Bityutskiy
-
1. Make the I/O debugging message print the journal head number.
2. Add prints to timer functions.Signed-off-by: Artem Bityutskiy
-
Fix the following warning:
fs/ubifs/io.c: In function 'ubifs_wbuf_init':
fs/ubifs/io.c:860: warning: integer overflow in expressionAnd limit maximum hrtimer delta to ULONG_MAX because the
argument is 'unsigned long'.Signed-off-by: Adrian Hunter
Signed-off-by: Artem Bityutskiy
08 Jun, 2009
1 commit
-
UBIFS uses timers for write-buffer write-back. It is not
crucial for us to write-back exactly on time. We are fine
to write-back a little earlier or later. And this means
we may optimize UBIFS timer so that it could be groped
with a close timer event, so that the CPU would not be
waken up just to do the write back. This is optimization
to lessen power consumption, which is important in
embedded devices UBIFS is used for.hrtimers have a nice feature: they are effectively range
timers, and we may defind the soft and hard limits for
it. Standard timers do not have these feature. They may
only be made deferrable, but this means there is effectively
no hard limit. So, we will better use hrtimers.Signed-off-by: Artem Bityutskiy
27 Jan, 2009
1 commit
-
When data CRC checking is disabled, UBIFS returns incorrect return
code from the 'try_read_node()' function (0 instead of 1, which means
CRC error), which make the caller re-read the data node again, but using
a different code patch, so the second read is fine. Thus, we read the
same node twice. And the result of this is that UBIFS is slower
with no_chk_data_crc option than it is with chk_data_crc option.
This patches fixes the problem.Reported-by: Reuben Dowle
Signed-off-by: Artem Bityutskiy
30 Sep, 2008
2 commits
-
When UBIFS switches to R/O mode because of an error,
it is reasonable to enable data CRC checking.Signed-off-by: Artem Bityutskiy
-
UBIFS read performance can be improved by skipping the CRC
check when data nodes are read. This option can be used if
the underlying media is considered to be highly reliable.
Note that CRCs are always checked for metadata.Read speed on Arm platform with OneNAND goes from 19 MiB/s
to 27 MiB/s with data CRC checking disabled.Signed-off-by: Adrian Hunter
13 Aug, 2008
1 commit
-
We use ubifs_ro_mode() quite a lot, and not in fast-path, so
there is no reason to blow the code up by having it inlined.
Also, we usually want R/O mode change to be seen to other
CPUs as soon as possible, so when we make this a function
call, we will automatically have a memory barrier.Signed-off-by: Adrian Hunter
Signed-off-by: Artem Bityutskiy
15 Jul, 2008
1 commit
-
This is a new flash file system. See
http://www.linux-mtd.infradead.org/doc/ubifs.htmlSigned-off-by: Artem Bityutskiy
Signed-off-by: Adrian Hunter