Re: What is the truth about Linux 2.4's RAM limitations?

From: Timur Tabi (ttabi@interactivesi.com)
Date: Tue Jul 10 2001 - 13:01:53 EST

Next message: Chris Wedgwood: "Re: NFS Client patch"
Previous message: Andreas Dilger: "Re: 2.4.6-preX, 2.4.6..."
In reply to: Richard B. Johnson: "Re: What is the truth about Linux 2.4's RAM limitations?"
Next in thread: Jonathan Lundell: "Re: What is the truth about Linux 2.4's RAM limitations?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Richard B. Johnson wrote:

>The kernel has the capability (by design) of addressing anything it
>wants. So, if this is what you mean by "shared", I guess you imply
>that Windows can't address anything it wants? Of course it can.
>

Well, I may have oversimplified it a bit. My point was that a given
Windows driver can't just take a 32-bit pointer and pass it to another
driver and have it just work like that.

-- Timur Tabi Interactive Silicon

- 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/

Next message: Chris Wedgwood: "Re: NFS Client patch"
Previous message: Andreas Dilger: "Re: 2.4.6-preX, 2.4.6..."
In reply to: Richard B. Johnson: "Re: What is the truth about Linux 2.4's RAM limitations?"
Next in thread: Jonathan Lundell: "Re: What is the truth about Linux 2.4's RAM limitations?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Sun Jul 15 2001 - 21:00:12 EST