Date: Fri, 18 Nov 2016 11:45:59 -0800 From: Conrad Meyer <cem@freebsd.org> To: Matthias Andree <matthias.andree@gmx.de> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: sbrk(0) replacement for memory resource tracking? Message-ID: <CAG6CVpVrkhPX%2B9dJaUwsCVnfPCXu2Br%2Bn5FEi99JjsDNvsDa_g@mail.gmail.com> In-Reply-To: <56d3f59d-29e7-f98d-af25-e39c51a85f11@gmx.de> References: <20161110012624.GA23701@lonesome.com> <dd964b1d-db3c-94d4-794b-929b28326430@gmx.de> <20161110215549.GL91607@kduck.kaduk.org> <a8a85ea4-b9af-cc6a-0573-d23967b4d82c@gmx.de> <CAPyFy2BD=0exCq=1odNo6=5x%2BUyZUVs%2BmB37K_mG=6fVBOowUQ@mail.gmail.com> <56d3f59d-29e7-f98d-af25-e39c51a85f11@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Nov 18, 2016 at 1:09 AM, Matthias Andree <matthias.andree@gmx.de> wrote: > Before going the jemalloc-example way in e2fsprogs, I'd contact the > upstream maintainer if that's sensible at all, because it's mostly a > maintainer/developer feature for a tool set that originates in Linux, > and given we don't have ext3/ext4 write support in the FreeBSD kernels > currently, nor a FUSE module TTBOMK, I think e2fsprogs will remain in a > niche. Hi Matthias, Actually, FreeBSD can R/W ext4 (and ext3/ext2) very happily with the sysutils/fusefs-lkl port :-). It can also read/write XFS and some kinds of BTRFS images. Best, Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpVrkhPX%2B9dJaUwsCVnfPCXu2Br%2Bn5FEi99JjsDNvsDa_g>