From: Gustavo Chain <g@0xff.cl>
To: linux-kernel@vger.kernel.org
Subject: Re: howto boost write(2) performance?
Date: Tue, 9 Oct 2007 10:19:16 -0400 [thread overview]
Message-ID: <20071009101916.5a7f5c19@0xff.cl> (raw)
In-Reply-To: <1191937817.3641.9.camel@blackberry>
El Tue, 09 Oct 2007 15:50:17 +0200
Michael Stiller <ms@2scale.net> escribió:
> Hi list,
>
> i'm developing an application (in C) which needs to write about
> 1Gbit/s (125Mb/s) to a disk array attached via U320 SCSI.
> It runs on Dual Core 2 Xeons @2Ghz utilizing kernel 2.6.22.7.
>
> I buffer the data in (currently 4) 400Mb buffers and use write(2) in a
> dedicated thread to write them to the raw disk (no fs).
>
> The write(2) performance is not good enough, the writer threads take
> to much time, and i ask you for ideas, howto to boost the write
> performance.
>
> Maybe mmaping the disk would work?
>
> Cheers,
>
> -Michael
>
> PS. I would like to be cc'd as i usually don't read the list due to
> high traffic.
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
Create a 1GB ram disk, write data there, and then backup into a hard
disk
--
Gustavo Chaín Dumit
next prev parent reply other threads:[~2007-10-09 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 13:50 howto boost write(2) performance? Michael Stiller
2007-10-09 10:25 ` Nick Piggin
2007-10-10 6:26 ` Michael Stiller
2007-10-09 14:19 ` Gustavo Chain [this message]
2007-10-09 14:56 ` Andi Kleen
2007-10-09 15:42 ` Boaz Harrosh
2007-10-09 16:26 ` Michael Tokarev
2007-10-11 13:50 ` Michael Stiller
2007-10-17 22:19 ` 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=20071009101916.5a7f5c19@0xff.cl \
--to=g@0xff.cl \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.