Bug 13463
Summary: | Poor SSD performance | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Jake (ellowitz) |
Component: | Serial ATA | Assignee: | Jeff Garzik (jgarzik) |
Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
Severity: | normal | CC: | akpm, alan, rjw, tj |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.29.4 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 12398 | ||
Attachments: |
Kernel 2.6.29 log file
dmesg from booting kernel 2.6.29 2.6.29.4 kernel boot log. 2.6.28.10 kernel boot log. |
Description
Jake
2009-06-05 17:37:07 UTC
I marked this as a regression. Can you please attach boot logs from the two kernels? Created attachment 21781 [details]
Kernel 2.6.29 log file
Comment on attachment 21781 [details]
Kernel 2.6.29 log file
This file corresponds to booting kernel 2.6.29 when I get slow SSD reads.
Created attachment 21782 [details]
dmesg from booting kernel 2.6.29
I also can submit kernel.log and dmesg from boots of the 2.6.28.10 kernel in which I get full read speeds. I will do this if you think it is necessary. Yeap, that was what I meant by "the two kernels". Sorry about not being clear. Also, you attached 25 and 20 byte files which only contain the file names. Created attachment 21785 [details]
2.6.29.4 kernel boot log.
Created attachment 21786 [details]
2.6.28.10 kernel boot log.
I'm sorry, I should have checked the files before uploading them. The proper files are now uploaded. Hmm... can't see any ATA related differences. Can you please run the following command as root in 2.6.28 and 29 and report the results? # dd if=/dev/sda of=/dev/null iflag=direct bs=1M count=1024 Thanks. In 2.6.28 and 2.6.29 the direct flag gives me 230 MB/s reads. In the original report, what 'other tests' showed large performance regression other than hdparm? Also, does hdparm give consistent numbers over multiple trials? dd if=/dev/sda of=/dev/null also gives me read speeds of 70-80 MB/s in 2.6.29, where I get 220 MB/s in 2.6.28. Hmm... I see. The difference is from far above the block/storage layer. Most likely vm. Andrew, can you please take it? Thanks. I installed a version of the 2.6.30 kernel and this problem appears to be absent since I got read speeds of 220MB/s. Apparently this problem is isolated to the 2.6.29 kernel. Heh... so it solved itself. It would be nice to find out which was the culprit. I suppose the right people would already know. Anyways, with 2.6.30 already out of the door, I don't think it's of high priority. Jeff, can you please close this one? Thanks. |