On 6/22/05, Thomas Hellström <[EMAIL PROTECTED]> wrote: > 1) How is allocating a second fixed sarea different from splitting the > first SAREA in two parts? The problem is not space but future expandability > and generality.
Both the DRM and driver sarea structs go into the first SHM. You can use the second one for whatever you want. We have to leave the organization of the first SHM alone to keep existing binaries working. Drivers without XvMC support won't create the second SHM. > 2) How is a non-root drmAddMap for shared memory a bigger security risc > than shmget? I understand why SAREA containing the lock needs to be > permanent, but not subsequent ones. Why can't they be created on demand by > the master? The memory being allocated by the drivers is non-swappable kernel memory. shmget is allocating swapable memory. Device drivers can't user swapable memory. There is a limited amout of kernel space memory available. > /Thomas > > > > > > > /Thomas > > > > > > > > > > > -- Jon Smirl [EMAIL PROTECTED] ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
