From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de ([195.135.220.15]:60671 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752222AbdADLr2 (ORCPT ); Wed, 4 Jan 2017 06:47:28 -0500 Date: Wed, 4 Jan 2017 12:47:25 +0100 From: Jan Kara To: Amir Goldstein Cc: Jan Kara , Eric Paris , linux-fsdevel Subject: Re: [RFC][PATCH 0/4] fsnotify: pass single mark to handle_event() Message-ID: <20170104114725.GQ3780@quack2.suse.cz> References: <1482867148-31497-1-git-send-email-amir73il@gmail.com> <20170104082844.GH3780@quack2.suse.cz> <20170104103958.GN3780@quack2.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed 04-01-17 12:45:41, Amir Goldstein wrote: > On Wed, Jan 4, 2017 at 12:39 PM, Jan Kara wrote: > > On Wed 04-01-17 11:57:04, Amir Goldstein wrote: > ... > >> Yes, I am aware of those testcases. > >> I find LTP quite heavy to build, so I though I would spin a dedicated > >> testsuite that will contain your testcases, but will also include > >> infrastructure for stress testing and profiling. > >> Keeping track of performance regressions is clearly a major aspect > >> of maintaining fsnotify. > > > > Yeah, I don't build full LTP, just testcases in those two directories. > > LTP seems to have this massive build system around it. > So just to give me a head start, do you use any custom build scripts > to build just those testcases? or simple make inside their directory > will do the trick (it didn't seem so simple from first look). I just run make inside the directories I'm interested in... Honza -- Jan Kara SUSE Labs, CR