From owner-freebsd-current@freebsd.org Sun Feb 18 20:15:30 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A7A8F26E22 for ; Sun, 18 Feb 2018 20:15:30 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 010A66907B for ; Sun, 18 Feb 2018 20:15:30 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id B141AF26E1F; Sun, 18 Feb 2018 20:15:29 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EBF6F26E1E for ; Sun, 18 Feb 2018 20:15:29 +0000 (UTC) (envelope-from agapon@gmail.com) Received: from mail-lf0-f54.google.com (mail-lf0-f54.google.com [209.85.215.54]) (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 13D2569076; Sun, 18 Feb 2018 20:15:28 +0000 (UTC) (envelope-from agapon@gmail.com) Received: by mail-lf0-f54.google.com with SMTP id x196so10395873lfd.12; Sun, 18 Feb 2018 12:15:28 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=kqOzPpO/uUcMWgeWZc8aZMTDfT+bO29eVemhVrldIt8=; b=Z2b5paTMfHeukcR5iLZkFfN4tDiyXQpAC16LEgcXIFoEIAErkVKjVGiNwJGO6CiF4G zoXZ/sRLUO/Jspu+isnYHlCZ9wTZqGvzDcD7cWPIGPiPc66hpfwftn2+w3VZrTLy2uT+ sV+uiuZt3jE8vUxQwbRryyjkCqWzgm5Srzbtcb9JY13AqNnNW6eBgLs6qIXS7LX7JZd2 X4RCYD8TJiRqr5xzKzd3mIds9MNtEMd9PU1WPHHhaj9rYQN9hV9xjbzZ5LTFEBkv/mTg DIujOHm3ra7I58mEcd3hgpE0YNQU8VHM6HK84rtXWab7B97pmi9yfbhmzkq0oer8J1jK JYYA== X-Gm-Message-State: APf1xPByKlvBdw/do/d4yjBwOLysGwzgvzsAS7Z5Mob+SR6aRA3w72ex Gr/gV7cLaeCIU4csjjxQm6MY8AIm X-Google-Smtp-Source: AH8x225V3O9Hkd83eXOjqb2Bt4bXIiiTzZ7Lzg+kbVQFzwVTDWcGk8O/0hNusFco1oBKCx9Fk8H/Mg== X-Received: by 10.25.149.143 with SMTP id x137mr8611598lfd.119.1518984927115; Sun, 18 Feb 2018 12:15:27 -0800 (PST) Received: from [192.168.0.88] (east.meadow.volia.net. [93.72.151.96]) by smtp.googlemail.com with ESMTPSA id e27sm3630243lff.89.2018.02.18.12.15.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Feb 2018 12:15:25 -0800 (PST) Subject: Re: Since last week (today) current on my Ryzen box is unstable To: Gleb Smirnoff Cc: Andrew Reilly , kib@FreeBSD.org, current@FreeBSD.org References: <0CEA9D55-D488-42EC-BBDE-D0B7CE58BAEA@bigpond.net.au> <20180218023545.GE93303@FreeBSD.org> <431f3e00-c66a-8e2e-6c61-a315a6353d1d@FreeBSD.org> <20180218132623.GF93303@FreeBSD.org> From: Andriy Gapon Message-ID: <359681a7-3885-820e-1ac8-19254c83d1ad@FreeBSD.org> Date: Sun, 18 Feb 2018 22:15:24 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180218132623.GF93303@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Feb 2018 20:15:30 -0000 On 18/02/2018 15:26, Gleb Smirnoff wrote: > My only point is that it is a performance improvement. IMHO that's enough :) I don't think that passing an invalid argument to a documented KPI is "enough" for any optimization. > If you can't suggest a more elegant way of doing that improvement, then all > I can suggest is to document it and add its support to ZFS. In return I can only suggest that (1) you run your suggestion by arch@ -- unless that's already been done and you can point me to the discussion, (2) document it and (3) double-check that all implementations confirm to it. -- Andriy Gapon