Date: Mon, 7 Feb 2011 13:42:43 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Ivan Voras <ivoras@freebsd.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Scheduler question Message-ID: <772B352C-7241-4326-8B49-3FB675896609@gsoft.com.au> In-Reply-To: <AANLkTincOBWKhr9qWX_dFmukWeUCG61aYT0AXd-VYYTu@mail.gmail.com> References: <53A394ED-7C2E-4E4B-A9A7-CB5F1B27DBE3@gsoft.com.au> <iignas$kbc$1@dough.gmane.org> <AA0DA14A-A8E5-48C5-AABE-ECCB02C59D19@gsoft.com.au> <iii67s$ngs$1@dough.gmane.org> <7108E013-77D1-47F8-892E-5027DB7D432B@gsoft.com.au> <990005CD-39BD-45F6-BD07-ACEE79DF5A03@gsoft.com.au> <AANLkTincOBWKhr9qWX_dFmukWeUCG61aYT0AXd-VYYTu@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/02/2011, at 13:02, Ivan Voras wrote: >>> I'll be looking at it on Monday, I will let you know :) >>=20 >> No luck with mlock() so it wouldn't appear to be paging is the issue = :( >=20 > I'm also interested in raw device vs file system access! Oops, sorry.. I just tried that now but it doesn't improve things :( I am writing directly to /dev/ad10 but stressing /dev/ad14 (sudo tar -cf = /dev/null /local0) It is interesting also that if I have md5's soaking up CPU then it's = much less likely to start streaming properly and generally bombs out = straight away. If I start it streaming and then start md5 it stays = running... (even if it's rtprio'd) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?772B352C-7241-4326-8B49-3FB675896609>