On Thu, Nov 03, 2005 at 03:37:44PM +0000, Hugh Dickins wrote:
> > > I don't much want to add another path into copy_pte_range, actually
> > > copying pages. If the process really wants DMA into such areas,
> > > then it should contain the code for the child to COW them itself?
> >
> > How do you do that, say, for a stack page, or global data section?
>
> And why do you need to?
>
> You seem to be saying, actually DONTCOPY isn't enough of a solution,
> we need something else instead.
>
DONTCOPY is a good solution for the problem it solves, but there are
other problems :). One of them is what should we do if only part of the
page is used for DMA and other part contains information needed by the
forked child? We can copy such pages on fork or declare such state to be
user error. I can live with both.
--
Gleb.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
