On Fri, Jun 21, 2013 at 1:42 PM, Holger Hans Peter Freyther <hol...@freyther.de> wrote: > On Fri, Jun 21, 2013 at 12:29:56PM +0200, Kay Sievers wrote: > >> What's the problem with using address *space*? Address space is not >> used memory, file memory mappings are just how things work in general, >> they are cheap and should not really matter. > > It is a symptom of inefficiency. If an application maps 130MB of memory > to manage what should be a 648kb ringbuffer it raises some doubts. The > danger comes from the question if the journald will fragment its memory > in a way that a real memory allocation will fail because there is no space > left in the virtual address space. > > The above concern would be easier to resolve if used and mapped memory > would be within reasonable bounds when managing just some kb of data.
Fragmentation, allocation? I don't think we talk about the same thing here. Mapping an on-disk file "a symptom of inefficiency", you might need to update your idea of how things work. Kay _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
