login::
pass::
name::
id::
node:
Re: direct disk access
template:
4
parent:
direct disk access
owner:
maniac
viewed by:
created:
28.01.2010 - 23:44:43
cwbe coordinatez
:
101
63540
63542
2109677
1857521
5154014
5154044
ABSOLUT
K
YBERIA
permissions
you:
r,
system:
public
net:
yes
⠪
neurons
stats
|
by_visit
|
by_K
source
tiamat
K
|
my_K
|
given_K
last
commanders
polls
total descendants::3
total children::1
show[
2
|
3
]
flat
no teda este ze pri ddckovani z /dev/disk0 je pocet IO x-nasobne vyssi ako pri praci s filesystemom
title/content
title
content
user
0000010100063540000635420210967701857521051540140515404405154200
forcer
29.01.2010 - 01:17:50
, level: 1,
UP
NEW
Re[2]: direct disk access
nebude to koli cached/uncached write?
000001010006354000063542021096770185752105154014051540440515420005154570
maniac
29.01.2010 - 10:53:03
, level: 2,
UP
NEW
Re[3]: direct disk access
znelo by to logicky, ale co chces cacheovat na sekvencnom citani z block devicu? na velkosti blocksize (skusal som to do 16MB) vobec nezalezalo :(
a teda subor som mal vacsi ako 4GB co je velkost mojej RAMky, aby ten DD zo suboru necacheoval..
skor mi to pride ze mach nejak osetruje/emuluje priamy pristup k blokovemu zariadeniu a neni to robene efektive
00000101000635400006354202109677018575210515401405154044051542000515457005157394
paket
30.01.2010 - 21:46:09
, level: 3,
UP
NEW
Re[4]: direct disk access
macfuse projekt uvádzal absenciu cache ako hlavný dôvod slabého výkonu ntfs-3g pre macfuse
tipujem cache, ale to je tak všetko z mojej strany