You've spoiled the fun. I've was enjoying watching this rather weird discussion pan out.
What's next? Compiling drivers into the kernel?
:)
-----Original Message----- From: ros-dev-bounces@reactos.org [mailto:ros-dev-bounces@reactos.org] On Behalf Of Alex Ionescu Sent: 12 November 2009 15:43 To: ReactOS Development List Subject: Re: [ros-dev] A reimplementation of reactos' cache manager supporting alternate filesystems better (including ext2)
It's always funny to see how most people on this list talking about NT really have no clue.
There would be no advantage to have a swap partition on Windows. Fast I/O and Paging I/O more than make up for any "benefits" Linux has. It's easy to have benefits to skip your FS when your FS model is worthless. It becomes a much mooter point when your FS model is the size and complexity (in terms of performance) of the competition's kernel. Not to mention you could forget about crash dumps with a separate partition.
And no, Windows 7 sets up a separate system volume (this is where boot files go) to separate from the Win7 boot volume (this is where the Windows system files go) and to allow BitLocker to work.
Best regards, Alex Ionescu
On Thu, Nov 12, 2009 at 3:18 AM, Love Nystrom love.nystrom@gmail.com wrote:
Brian wrote:
i was always under the impression that having a swap partition meant that you did not have to hassle with the file system allowing for marginal performance boosts.
That is generally true. In theory, APIs to access a swap partition can be implemented to use the disk device driver directly, removing the
additional
processing incurred by file systems drivers.
In practice on NT, I believe the proper way is to implement a swap file system driver, which can be made more efficient than regular file systems drivers.
Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev
_______________________________________________ Ros-dev mailing list Ros-dev@reactos.org http://www.reactos.org/mailman/listinfo/ros-dev