2019-05-29 16:57:41 -07:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-08 12:02:39 +02:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2015-10-22 20:29:54 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
percpu.h is included by sched.h and module.h and thus ends up being
included when building most .c files. percpu.h includes slab.h which
in turn includes gfp.h making everything defined by the two files
universally available and complicating inclusion dependencies.
percpu.h -> slab.h dependency is about to be removed. Prepare for
this change by updating users of gfp and slab facilities include those
headers directly instead of assuming availability. As this conversion
needs to touch large number of source files, the following script is
used as the basis of conversion.
http://userweb.kernel.org/~tj/misc/slabh-sweep.py
The script does the followings.
* Scan files for gfp and slab usages and update includes such that
only the necessary includes are there. ie. if only gfp is used,
gfp.h, if slab is used, slab.h.
* When the script inserts a new include, it looks at the include
blocks and try to put the new include such that its order conforms
to its surrounding. It's put in the include block which contains
core kernel includes, in the same order that the rest are ordered -
alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
doesn't seem to be any matching order.
* If the script can't find a place to put a new include (mostly
because the file doesn't have fitting include block), it prints out
an error message indicating which .h file needs to be added to the
file.
The conversion was done in the following steps.
1. The initial automatic conversion of all .c files updated slightly
over 4000 files, deleting around 700 includes and adding ~480 gfp.h
and ~3000 slab.h inclusions. The script emitted errors for ~400
files.
2. Each error was manually checked. Some didn't need the inclusion,
some needed manual addition while adding it to implementation .h or
embedding .c file was more appropriate for others. This step added
inclusions to around 150 files.
3. The script was run again and the output was compared to the edits
from #2 to make sure no file was left behind.
4. Several build tests were done and a couple of problems were fixed.
e.g. lib/decompress_*.c used malloc/free() wrappers around slab
APIs requiring slab.h to be added manually.
5. The script was run on all .h files but without automatically
editing them as sprinkling gfp.h and slab.h inclusions around .h
files could easily lead to inclusion dependency hell. Most gfp.h
inclusion directives were ignored as stuff from gfp.h was usually
wildly available and often used in preprocessor macros. Each
slab.h inclusion directive was examined and added manually as
necessary.
6. percpu.h was updated not to include slab.h.
7. Build test were done on the following configurations and failures
were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
distributed build env didn't work with gcov compiles) and a few
more options had to be turned off depending on archs to make things
build (like ipr on powerpc/64 which failed due to missing writeq).
* x86 and x86_64 UP and SMP allmodconfig and a custom test config.
* powerpc and powerpc64 SMP allmodconfig
* sparc and sparc64 SMP allmodconfig
* ia64 SMP allmodconfig
* s390 SMP allmodconfig
* alpha SMP allmodconfig
* um on x86_64 SMP allmodconfig
8. percpu.h modifications were reverted so that it could be applied as
a separate patch and serve as bisection point.
Given the fact that I had only a couple of failures from tests on step
6, I'm fairly confident about the coverage of this conversion patch.
If there is a breakage, it's likely to be something in one of the arch
headers which should be easily discoverable easily on most builds of
the specific arch.
Signed-off-by: Tejun Heo <tj@kernel.org>
Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
2010-03-24 17:04:11 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2012-05-18 18:44:53 +03:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
|
|
|
|
|
2011-10-30 00:11:53 +02:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-08 12:02:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-22 20:29:54 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2011-02-08 12:02:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-21 19:07:12 -07:00
|
|
|
|
2011-02-08 12:02:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-12-23 15:25:39 +02:00
|
|
|
|
2011-02-08 12:02:40 +02:00
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2011-02-08 12:02:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2014-07-21 19:07:12 -07:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2013-08-15 22:55:09 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-21 19:07:12 -07:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2013-08-15 22:55:09 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2014-07-21 19:07:12 -07:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2013-08-15 22:55:09 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-15 22:55:09 +09:00
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-21 19:07:12 -07:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2013-08-15 22:55:08 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2014-07-21 19:07:12 -07:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2013-08-15 22:55:08 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2014-07-21 19:07:12 -07:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2013-08-15 22:55:08 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2013-08-15 22:55:08 +09:00
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-22 20:29:54 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-10-22 20:29:54 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
mtd: tests: Fix eraseblock read speed miscalculation for lower partition sizes
While calculating speed during mtd_speedtest, the time interval
(i.e., start - finish) is rounded off to the nearest milliseconds by
ignoring the fractional part. This leads to miscalculation of speed.
The miscalculation is more visible while running speed test on small
partition sizes(i.e., when partition size is equal to eraseblock size or
twice the eraseblock size) at higher spi frequencies.
For e.g., while calculating eraseblock read speed for a mtd partition with
size equal to the eraseblock size(i.e., 64KiB) the eraseblock read time
interval comes out to be 966490 nanosecond. This is then converted to
millisecond(i.e., 0.966 msec.). The integer part (i.e., 0 msec) of the
value is considered and the fractional part (i.e., 0.966) is ignored,for
calculating the eraseblock read speed. So the reported eraseblock read
speed is 0 KiB/s, which is incorrect.
There are two approaches to fix this issue.
First approach will be to keep the time interval in millisecond. and round
up the integer value, with this approach the 0.966msec time interval in the
above example will be rounded up to 1msec and this value is used for
calculating the speed. Downside of this approach is that the reported speed
is still not accurate.
Second approach will be to convert the time interval to microseconds
instead of milliseconds, with this approach the 966490 nanosecond time
interval in the above example will be converted t0 966.490usec and this
value is used for calculating the speed. As compared to the current
implementation and the suggested First approach, this approach will report
a more accurate speed. Downside of this approach is that, in future if the
mtd size is too large then the u64 variable, that holds the number of
bytes, might overflow.
In this patch we have gone with the second approach as this reports a more
accurate speed. With this approach the eraseblock read speed in the above
example comes out to be 132505 KiB/s when the spi clock is configured at
150Mhz.
Signed-off-by: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20220208103905.13354-1-amit.kumar-mahapatra@xilinx.com
2022-02-08 16:09:05 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
mtd: tests: Fix eraseblock read speed miscalculation for lower partition sizes
While calculating speed during mtd_speedtest, the time interval
(i.e., start - finish) is rounded off to the nearest milliseconds by
ignoring the fractional part. This leads to miscalculation of speed.
The miscalculation is more visible while running speed test on small
partition sizes(i.e., when partition size is equal to eraseblock size or
twice the eraseblock size) at higher spi frequencies.
For e.g., while calculating eraseblock read speed for a mtd partition with
size equal to the eraseblock size(i.e., 64KiB) the eraseblock read time
interval comes out to be 966490 nanosecond. This is then converted to
millisecond(i.e., 0.966 msec.). The integer part (i.e., 0 msec) of the
value is considered and the fractional part (i.e., 0.966) is ignored,for
calculating the eraseblock read speed. So the reported eraseblock read
speed is 0 KiB/s, which is incorrect.
There are two approaches to fix this issue.
First approach will be to keep the time interval in millisecond. and round
up the integer value, with this approach the 0.966msec time interval in the
above example will be rounded up to 1msec and this value is used for
calculating the speed. Downside of this approach is that the reported speed
is still not accurate.
Second approach will be to convert the time interval to microseconds
instead of milliseconds, with this approach the 966490 nanosecond time
interval in the above example will be converted t0 966.490usec and this
value is used for calculating the speed. As compared to the current
implementation and the suggested First approach, this approach will report
a more accurate speed. Downside of this approach is that, in future if the
mtd size is too large then the u64 variable, that holds the number of
bytes, might overflow.
In this patch we have gone with the second approach as this reports a more
accurate speed. With this approach the eraseblock read speed in the above
example comes out to be 132505 KiB/s when the spi clock is configured at
150Mhz.
Signed-off-by: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20220208103905.13354-1-amit.kumar-mahapatra@xilinx.com
2022-02-08 16:09:05 +05:30
|
|
|
|
|
|
|
|
|
2011-03-07 12:00:46 +02:00
|
|
|
|
mtd: tests: Fix eraseblock read speed miscalculation for lower partition sizes
While calculating speed during mtd_speedtest, the time interval
(i.e., start - finish) is rounded off to the nearest milliseconds by
ignoring the fractional part. This leads to miscalculation of speed.
The miscalculation is more visible while running speed test on small
partition sizes(i.e., when partition size is equal to eraseblock size or
twice the eraseblock size) at higher spi frequencies.
For e.g., while calculating eraseblock read speed for a mtd partition with
size equal to the eraseblock size(i.e., 64KiB) the eraseblock read time
interval comes out to be 966490 nanosecond. This is then converted to
millisecond(i.e., 0.966 msec.). The integer part (i.e., 0 msec) of the
value is considered and the fractional part (i.e., 0.966) is ignored,for
calculating the eraseblock read speed. So the reported eraseblock read
speed is 0 KiB/s, which is incorrect.
There are two approaches to fix this issue.
First approach will be to keep the time interval in millisecond. and round
up the integer value, with this approach the 0.966msec time interval in the
above example will be rounded up to 1msec and this value is used for
calculating the speed. Downside of this approach is that the reported speed
is still not accurate.
Second approach will be to convert the time interval to microseconds
instead of milliseconds, with this approach the 966490 nanosecond time
interval in the above example will be converted t0 966.490usec and this
value is used for calculating the speed. As compared to the current
implementation and the suggested First approach, this approach will report
a more accurate speed. Downside of this approach is that, in future if the
mtd size is too large then the u64 variable, that holds the number of
bytes, might overflow.
In this patch we have gone with the second approach as this reports a more
accurate speed. With this approach the eraseblock read speed in the above
example comes out to be 132505 KiB/s when the spi clock is configured at
150Mhz.
Signed-off-by: Amit Kumar Mahapatra <amit.kumar-mahapatra@xilinx.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20220208103905.13354-1-amit.kumar-mahapatra@xilinx.com
2022-02-08 16:09:05 +05:30
|
|
|
|
|
|
|
|
|
2011-03-07 12:00:46 +02:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-08 12:02:40 +02:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-10-30 00:11:53 +02:00
|
|
|
|
|
|
|
|
|
2012-11-09 23:20:58 +09:00
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2011-10-30 00:11:53 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-08 12:02:39 +02:00
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2011-02-08 12:02:39 +02:00
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2010-01-06 10:48:18 +01:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-08 12:02:39 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2013-05-02 14:18:51 -07:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2022-10-05 17:49:46 +02:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-29 21:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-29 21:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-29 21:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-29 21:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-29 21:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-29 21:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2013-08-03 18:52:12 +09:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
2011-02-08 12:02:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2011-02-08 12:02:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2015-03-29 21:52:06 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2011-02-08 12:02:40 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2011-02-08 12:02:40 +02:00
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2012-10-10 23:10:02 +05:30
|
|
|
|
2008-12-08 13:36:18 +02:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|