From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Phillips Subject: Re: Tux3 Report: How fast can we =?iso-8859-1?Q?fsync=3F?= Date: Tue, 28 Apr 2015 23:56:11 -0700 Message-ID: <64c18eff-355a-454d-bacf-24362fe61c11@phunq.net> References: <8f886f13-6550-4322-95be-93244ae61045@phunq.net> <1430274071.3363.4.camel@gmail.com> <1906f271-aa23-404b-9776-a4e2bce0c6aa@phunq.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Cc: linux-fsdevel , tux3@tux3.org, Mike Galbraith , LKML , Theodore Ts'o To: Richard Weinberger Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tux3-bounces@phunq.net Sender: "Tux3" List-Id: linux-fsdevel.vger.kernel.org On Tuesday, April 28, 2015 11:20:08 PM PDT, Richard Weinberger wrote: > On Wed, Apr 29, 2015 at 8:01 AM, Daniel Phillips wrote: >> On Tuesday, April 28, 2015 7:21:11 PM PDT, Mike Galbraith wrote: ... > > Where can I find the fsync code? > IOW how to reproduce your results? :) Hi Richard, If you can bear with us, the latest code needs to make it through Hirofumi's QA before it appears on github. If you are impatient, the fsync in current head benchmarks pretty well too, I don't think I need to apologize for it. In any case, you build userspace tools from the hirofumi-user branch, by doing make in fs/tux3/user. This builds the tux3 command, and you make a filesystem with "tux3 mkfs ". You can build the kernel including Tux3 from the hirofumi branch, or the hirofumi-user branch, providing you do make clean SUBDIRS=fs/tux3 before building the kernel or make clean in tux3/user before building the user space, so user and kernel .o files don't collide. A little awkward indeed, but still it is pretty cool that we can even build that code for user space. The wiki might be helpful: https://github.com/OGAWAHirofumi/linux-tux3/wiki https://github.com/OGAWAHirofumi/linux-tux3/wiki/Compile This is current, except you want to build from hirofumi and hirofumi-user rather than master and user because the latter is a bit old. Regards, Daniel