From: Shriramana Sharma <samjnaa@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Improvements in 2.6.18 will help SATA?
Date: Tue, 26 Sep 2006 10:46:35 +0530 [thread overview]
Message-ID: <200609261046.35391.samjnaa@gmail.com> (raw)
I'm an end user, not a developer. From:
http://www.kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.18
I see that a lot of the changes are related to SATA. I have a Seagate SATA HDD
as my one and only HDD so if I will really be benefitting performance-wise
from the new features or improvements, then I will install 2.6.18 over
2.6.15. So please tell me as I am not able to decipher for myself, whether
these improvements will lead to better performance, efficiency, speed or
something like that on my SATA HDD.
Please don't be harsh with me if this question is way OT for this list. I
thought only the developers can answer such a question so I asked here. I'm
sincerely sorry if I am bothering anyone.
Please cc me as I am not on the list.
--
Shriramana Sharma
Linux user #395953 using Kubuntu 6.06.1
next reply other threads:[~2006-09-26 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 5:16 Shriramana Sharma [this message]
2006-09-27 17:40 ` Improvements in 2.6.18 will help SATA? Jonathan Stewart
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=200609261046.35391.samjnaa@gmail.com \
--to=samjnaa@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox