From owner-freebsd-bugs@freebsd.org  Tue Oct 20 16:37:08 2015
Return-Path: <owner-freebsd-bugs@freebsd.org>
Delivered-To: freebsd-bugs@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 32CF9A1A290
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Tue, 20 Oct 2015 16:37:08 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1E47BC2E
 for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 2015 16:37:08 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9KGb7sL032024
 for <freebsd-bugs@FreeBSD.org>; Tue, 20 Oct 2015 16:37:07 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 203891] Consider supporting linux' sync_file_range()
Date: Tue, 20 Oct 2015 16:37:07 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: feature, needs-patch, performance
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: crest@rlwinm.de
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-203891-8-eIj2WTGWqS@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203891-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-203891-8@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2015 16:37:08 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203891

crest@rlwinm.de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |crest@rlwinm.de

--- Comment #2 from crest@rlwinm.de ---
While not exactly what you're asking for FreeBSD does offer aio_fsync(2) to
implement asynchronous file syncing. In theory this offers the kernel the
opportunity to flush data to stable storage at the optimal pace and notify the
application about it. If we're talking about OS specific code paths its also
possible to receive the notification via kqueue(2) + kevent(2) instead of
polling or signals. Too bad that the kernel requires that much babysitting from
userland.

-- 
You are receiving this mail because:
You are the assignee for the bug.