From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyril Hrubis Date: Tue, 12 Sep 2017 16:08:59 +0200 Subject: [LTP] [PATCH v3 4/7] fzsync: Add functionality test for library In-Reply-To: <20170901130121.22821-4-rpalethorpe@suse.com> References: <20170901130121.22821-1-rpalethorpe@suse.com> <20170901130121.22821-4-rpalethorpe@suse.com> Message-ID: <20170912140859.GC29720@rei> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ltp@lists.linux.it Hi! > +/* > + * Copyright (c) 2017 Richard Palethorpe > + * > + * This program is free software: you can redistribute it and/or modify > + * it under the terms of the GNU General Public License as published by > + * the Free Software Foundation, either version 2 of the License, or > + * (at your option) any later version. > + * > + * This program is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the > + * GNU General Public License for more details. > + * > + * You should have received a copy of the GNU General Public License > + * along with this program. If not, see . > + */ > +/* Basic functionality test for tst_fuzzy_sync.h similar to the atomic tests > + * (test15.c). One thread writes to the odd indexes of an array while the > + * other writes to the even. If the threads are not synchronised then they > + * will probably write to the wrong indexes as they share an index variable > + * which they should take it in turns to update. > + */ I'm just wondering, wouldn't be a better test for the sync library if one of the threads does short usleep(); and we would check if the delay more or less corresponds to this value after some iterations? -- Cyril Hrubis chrubis@suse.cz