Dear Nail,
in message [EMAIL PROTECTED] you wrote:
quote
The second improvement is to remove a memory copy that is internal to the MD
driver. The MD
driver stages strip data ready to be written next to the I/O controller in a
page size pre-
allocated buffer. It is possible to bypass
On Thu, Feb 07, 2008 at 06:40:12AM +0100, Iustin Pop wrote:
On Thu, Feb 07, 2008 at 01:31:16AM +0100, Keld Jørn Simonsen wrote:
Anyway, why does a SATA-II drive not deliver something like 300 MB/s?
Wait, are you talking about a *single* drive?
Yes, I was talking about a single drive.
In
Keld Jørn Simonsen wrote:
Hi
I am looking at revising our howto. I see a number of places where a
chunk size of 32 kiB is recommended, and even recommendations on
maybe using sizes of 4 kiB.
Depending on the raid level, a write smaller than the chunk size causes
the chunk to be read,
In message [EMAIL PROTECTED] you wrote:
I actually think the kernel should operate with block sizes
like this and not wth 4 kiB blocks. It is the readahead and the elevator
algorithms that save us from randomly reading 4 kb a time.
Exactly, and nothing save a R-A-RW cycle if the
Wolfgang Denk wrote:
In message [EMAIL PROTECTED] you wrote:
I actually think the kernel should operate with block sizes
like this and not wth 4 kiB blocks. It is the readahead and the elevator
algorithms that save us from randomly reading 4 kb a time.
Exactly, and nothing save
On Wed, Feb 06, 2008 at 09:25:36PM +0100, Wolfgang Denk wrote:
In message [EMAIL PROTECTED] you wrote:
I actually think the kernel should operate with block sizes
like this and not wth 4 kiB blocks. It is the readahead and the elevator
algorithms that save us from randomly reading 4
On Thu, Feb 07, 2008 at 01:31:16AM +0100, Keld Jørn Simonsen wrote:
Anyway, why does a SATA-II drive not deliver something like 300 MB/s?
Wait, are you talking about a *single* drive?
In that case, it seems you are confusing the interface speed (300MB/s)
with the mechanical read speed (80MB/s).
On Wednesday February 6, [EMAIL PROTECTED] wrote:
We implemented the option to select kernel page sizes of 4, 16, 64
and 256 kB for some PowerPC systems (440SPe, to be precise). A nice
graphics of the effect can be found here:
On Wednesday February 6, [EMAIL PROTECTED] wrote:
Keld Jørn Simonsen wrote:
Hi
I am looking at revising our howto. I see a number of places where a
chunk size of 32 kiB is recommended, and even recommendations on
maybe using sizes of 4 kiB.
Depending on the raid level, a write
On Thursday February 7, [EMAIL PROTECTED] wrote:
Anyway, why does a SATA-II drive not deliver something like 300 MB/s?
Are you serious?
I high end 15000RPM enterprise grade drive such as the Seagate
Cheetah® 15K.6 Hard Drives only deliver 164MB/sec.
The SATA Bus might be able to deliver
On Tue, 5 Feb 2008, Keld Jørn Simonsen wrote:
Hi
I am looking at revising our howto. I see a number of places where a
chunk size of 32 kiB is recommended, and even recommendations on
maybe using sizes of 4 kiB.
My own take on that is that this really hurts performance.
Normal disks have a
11 matches
Mail list logo
