Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753533AbaLAMfR (ORCPT ); Mon, 1 Dec 2014 07:35:17 -0500 Received: from mx1.redhat.com ([209.132.183.28]:60931 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753236AbaLAMfP (ORCPT ); Mon, 1 Dec 2014 07:35:15 -0500 Date: Mon, 1 Dec 2014 14:34:55 +0200 From: "Michael S. Tsirkin" To: Cornelia Huck Cc: David Hildenbrand , linux-kernel@vger.kernel.org, David Miller , rusty@au1.ibm.com, nab@linux-iscsi.org, pbonzini@redhat.com, thuth@linux.vnet.ibm.com, Rusty Russell , virtualization@lists.linux-foundation.org, linux-api@vger.kernel.org Subject: Re: [PATCH v7 16/46] virtio_blk: v1.0 support Message-ID: <20141201123455.GA17958@redhat.com> References: <1417359787-10138-1-git-send-email-mst@redhat.com> <1417359787-10138-17-git-send-email-mst@redhat.com> <20141201091641.3085e682@thinkpad-w530> <20141201092658.GC15607@redhat.com> <20141201123315.1b95d06f.cornelia.huck@de.ibm.com> <20141201114645.GA17505@redhat.com> <20141201130258.6f01c1e3.cornelia.huck@de.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141201130258.6f01c1e3.cornelia.huck@de.ibm.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Dec 01, 2014 at 01:02:58PM +0100, Cornelia Huck wrote: > On Mon, 1 Dec 2014 13:46:45 +0200 > "Michael S. Tsirkin" wrote: > > > On Mon, Dec 01, 2014 at 12:33:15PM +0100, Cornelia Huck wrote: > > > On Mon, 1 Dec 2014 11:26:58 +0200 > > > "Michael S. Tsirkin" wrote: > > > > > > > For some places on data path, it might be worth it > > > > to cache the correct value e.g. as part of device > > > > structure. This replaces a branch with a memory load, > > > > so the gain would have to be measured, best done > > > > separately? > > > > > > I think we'll want to do some measuring once the basic structure is > > > in place anyway. > > > > What's meant by in place here? > > That this patchset is ready :) Also it's ready to the level where benchmarking is possible, right? I don't think you should wait until we finish polishing up commit messages. > > > > > We should make sure that e.g. s390 only takes minor > > > hit due to all that swapping that is needed for standard-compliant > > > devices. Caching the value might certainly help in some paths. > > > > Well, this is queued in linux-next for 3.19, so > > now's the time to do it :) > > So much to do, so little time... > > I'm still feeling a bit uncomfortable with some of the changes > (virtio-scsi etc.) as I have not been able to test them yet (as there's > no converted qemu for these yet). The virtio-net and virtio-blk changes > seem sane, though, and virtio-ccw should be fine as well. > > OTOH, it's not like we're introducing new external interfaces, so later > rework should be fine. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/