On Fri, 11 Aug 2006 10:15:35 +0400
Evgeniy Polyakov <[email protected]> wrote:
> On Thu, Aug 10, 2006 at 05:56:39PM -0700, Andrew Morton ([email protected]) wrote:
> > > Per kevent fd.
> > > I have some ideas about better mmap ring implementation, which would
> > > dinamically grow it's buffer when events are added and reuse the same
> > > place for next events, but there are some nitpics unresolved yet.
> > > Let's not see there in next releases (no merge of course), until better
> > > solution is ready. I will change that area when other things are ready.
> >
> > This is not a problem with the mmap interface per-se. If the proposed
> > event code permits each user to pin 160MB of kernel memory then that would
> > be a serious problem.
>
> The main disadvantage is that all memory is allocated on the start even
> if it will not be used later. I think dynamic grow is appropriate
> solution, since user will have that memory used anyway, since kevents
> are allocated, just part of them will be allocated from possibly
> mmaped memory.
But the worst-case remains the same, doesn't it? 160MB of pinned kernel
memory per user?
-
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]
