From: Erik Mouw <mouw@nl.linux.org>
To: Manish Regmi <regmi.manish@gmail.com>
Cc: Bill Davidsen <davidsen@tmr.com>,
linux-kernel@vger.kernel.org, kernelnewbies@nl.linux.org
Subject: Re: Linux disk performance.
Date: Thu, 21 Dec 2006 14:22:41 +0100 [thread overview]
Message-ID: <20061221132241.GA15226@gateway.home> (raw)
In-Reply-To: <652016d30612202203h16331f96o2147872db3cb2d43@mail.gmail.com>
On Thu, Dec 21, 2006 at 11:48:42AM +0545, Manish Regmi wrote:
> Yes... my application does large amount of I/O. It actually writes
> video data received from ethernet(IP camera) to the disk using 128 K
> chunks.
Bursty video traffic is really an application that could take advantage
from the kernel buffering. Unless you want to reinvent the wheel and do
the buffering yourself (it is possible though, I've done it on IRIX).
BTW, why are you so keen on smooth-at-the-microlevel writeout? With
real time video applications it's only important not to drop frames.
How fast those frames will go to the disk isn't really an issue, as
long as you don't overflow the intermediate buffer.
Erik
--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
next prev parent reply other threads:[~2006-12-21 13:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 4:07 Manish Regmi
2006-12-18 8:35 ` Arjan van de Ven
2006-12-18 12:39 ` Manish Regmi
2006-12-18 12:54 ` Nick Piggin
2006-12-18 13:07 ` Erik Mouw
2006-12-19 6:22 ` Manish Regmi
2006-12-19 6:38 ` Nick Piggin
2006-12-19 12:18 ` Arjan van de Ven
2006-12-20 11:17 ` Manish Regmi
2006-12-22 0:14 ` Bhanu Kalyan Chetlapalli
2006-12-22 5:30 ` Manish Regmi
2006-12-22 5:39 ` Bhanu Kalyan Chetlapalli
2006-12-22 5:56 ` Manish Regmi
2006-12-20 22:29 ` Bill Davidsen
2006-12-21 6:03 ` Manish Regmi
2006-12-21 7:15 ` Daniel Cheng
2006-12-21 13:22 ` Erik Mouw [this message]
2006-12-22 5:39 ` Manish Regmi
2006-12-27 15:50 ` Phillip Susi
2007-01-01 1:59 ` Bill Davidsen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061221132241.GA15226@gateway.home \
--to=mouw@nl.linux.org \
--cc=davidsen@tmr.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regmi.manish@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®