Messages in this thread | | | Subject | Re: [lkcd-devel] Re: What's left over. | From | (Eric W. Biederman) | Date | 09 Nov 2002 19:16:58 -0700 |
| |
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> On Sun, 2002-11-10 at 01:37, Eric W. Biederman wrote: > > The reasons I don't jump on board: > > - It does not handle multiple segments. > > Without multiple segments I think I simply out essential complexity > > of the problem. A bzImage has at least 2. > > Thats a matter for user space and the unpacker > > > - vmalloc is artificially limited to 128MB. > > Just grabbing a load of pages and using kmap/scatter gather by hand is > not
To use kmapped memory I need to setup a page table to do the final copy. And to setup a page table I need to know where the memory is going to be copied to.
So my gut impression at least says an interface that ignores where the image wants to live just adds complexity in other places, and makes for an interface that is hard to maintain long term, because you depend on a lot of kernel implementation details, which are likely to change in arbitrary ways.
Eric
- 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/
| |