From owner-freebsd-hackers@freebsd.org Fri Nov 18 19:46:08 2016 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 19B61C48093 for ; Fri, 18 Nov 2016 19:46:08 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f52.google.com (mail-it0-f52.google.com [209.85.214.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DD6878D3 for ; Fri, 18 Nov 2016 19:46:07 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f52.google.com with SMTP id c20so41739471itb.0 for ; Fri, 18 Nov 2016 11:46:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=Xb9Lfx7uk1jTTZZBJWITcbyT7JVCY49mRAipo7eAvGg=; b=bh2R059p1Ck8pSmba/vWFOA3Gx1jFwnm8WbKP7KJAclYIP3XIEJqvqRf9xn+20euuS SZtpYMXVBL1xfWY53CuSx54yP5BOIBqSkwV5mrdIEE85gfbtZ1/ymwxy9eA2UGkn4sr3 1wWRUpsulNNU2bOjTGo8vJEOBTDWrpWJb/hXhu4fkrgDyO05R4Ai2y/YYcJalPa+oPDm 6OtP5hT3s5QSeAtVmADc59gwnMVkFDtTp/Ov59WYTmwQvCgSR0wff0n5GXPyHI/jdDbC GSQqaX4eXrpT44ECBPHMy06mrCs+jSKOebQXcxKAG42ut1fIXQKn5PZAgm1isDEmUeTK gBiQ== X-Gm-Message-State: AKaTC02PKilIEmV4XtBxCZJi698vP83qB3BeRE00fdHjnowb48oRsYUUOAYoUr5POSv33A== X-Received: by 10.36.185.83 with SMTP id k19mr75162iti.59.1479498360583; Fri, 18 Nov 2016 11:46:00 -0800 (PST) Received: from mail-it0-f54.google.com (mail-it0-f54.google.com. [209.85.214.54]) by smtp.gmail.com with ESMTPSA id j189sm3456785ioe.14.2016.11.18.11.45.59 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 Nov 2016 11:46:00 -0800 (PST) Received: by mail-it0-f54.google.com with SMTP id y23so49903915itc.0 for ; Fri, 18 Nov 2016 11:45:59 -0800 (PST) X-Received: by 10.36.37.199 with SMTP id g190mr114779itg.66.1479498359774; Fri, 18 Nov 2016 11:45:59 -0800 (PST) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.36.220.199 with HTTP; Fri, 18 Nov 2016 11:45:59 -0800 (PST) In-Reply-To: <56d3f59d-29e7-f98d-af25-e39c51a85f11@gmx.de> References: <20161110012624.GA23701@lonesome.com> <20161110215549.GL91607@kduck.kaduk.org> <56d3f59d-29e7-f98d-af25-e39c51a85f11@gmx.de> From: Conrad Meyer Date: Fri, 18 Nov 2016 11:45:59 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: sbrk(0) replacement for memory resource tracking? To: Matthias Andree Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 19:46:08 -0000 On Fri, Nov 18, 2016 at 1:09 AM, Matthias Andree 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