On Wed, Sep 15, 2004 at 01:23:55AM -0700, David Mosberger wrote: > >>>>> On Tue, 14 Sep 2004 10:16:29 -0500, Robin Holt <holt@sgi.com> said: > > Robin> I would like to start with the general, what are we trying to > Robin> solve? I can not think of a single reason aside from the > Robin> previously discussed min state area for the kernel to ever > Robin> need to work with memory uncached. > > Uh, what about device drivers that want to map physical memory with > write-combine? Isn't that effectively what your fetchop driver does? That is exactly what it does, but I was wondering if there are other examples of drivers that do this. If not, I would still like to push for doing the minimum necessary to keep from designing something that has no users. > > Robin> Assuming there is no reason, can we pare this discussion back > Robin> to a page based allocator? That would be much simpler to > Robin> work with and would not need to recombine fragments. > > Quite possibly. It certainly seems reasonable to start that way. > > --david > - > To unsubscribe from this list: send the line "unsubscribe linux-ia64" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Wed Sep 15 07:06:42 2004
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:30 EST