On Fri, Jul 1, 2011 at 4:23 PM, Lennart Poettering <[email protected]> wrote: > On Fri, 01.07.11 16:06, Kok, Auke-jan H ([email protected]) wrote: > >> >> On Fri, Jul 1, 2011 at 3:50 PM, Lennart Poettering >> <[email protected]> wrote: >> > On Tue, 28.06.11 09:43, Michael Olbrich ([email protected]) wrote: >> > >> >> Hi, >> >> >> >> more stuff from the embedded front. On ARM hugetlbfs is not supported. The >> >> result is rather confusing for the user: >> >> At first /dev/hugepages exists. If I run "ls /dev/hugepages", >> >> "mount[494]: mount: unknown filesystem type 'hugetlbfs'" is logged and >> >> ls says "ls: /dev/hugepages: No such device". >> >> Afterwards /dev/hugepages is gone. >> > >> > We probably shouldn't install those mount and automount units at all on >> > ARM. Would be happy to take a patch that ifdefs this out with automake >> > conditions on the archs that don't support this. >> >> We don't have it enabled in MeeGo... not even for x86. > > Do have just the file system disabled or hugepage support at all? > > If you disabled just the fs, did you do that because it is an obsolete > interface? Or simply because it is primarily relevant for huge databases > and people presumably don't run those on Meego? ;-)
We don't even have HIGHMEM enabled, again not even for x86. HUGEPAGEs (transparent) are actually enabled, but I'm not entirely sure if we do have users for them in reality(although I could see we would), I can poke my friendly meego kernel maintainer if you'd really want to know ;) The biggest database we have on MeeGo installs is the rpm database.... Does that answer that part? Auke _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
