Received: by 10.223.185.116 with SMTP id b49csp6352010wrg; Wed, 28 Feb 2018 08:02:26 -0800 (PST) X-Google-Smtp-Source: AH8x226ZJBWWYx7zx+sssoR18no78WBnTzu5FcOsomjZoX9A7ze5+EF23zPb0BtkZiysBtfWvuxU X-Received: by 2002:a17:902:654a:: with SMTP id d10-v6mr18139692pln.117.1519833745919; Wed, 28 Feb 2018 08:02:25 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519833745; cv=none; d=google.com; s=arc-20160816; b=MQKkX1bNNLfnregRCe6bTIS83bQLjCu1TUdsPRG04xDjp7+OoWudv9oH8YNLXz5g9X 9B2gg62rBPHYIpHuj4vYM523wtaLGiX9rzTnaHEpKEgrtOqghHgyMUMo2nwEN6PlWKQm yaMjixV3gwKvmygKmFpRdbJMPj5p9zK9X/h7BKogktG43jC11RvW0fyEfkvIW5v45cRZ o6tfEVRvzO4DiQt75Vbqv5nRMav3/oqX7zRgABVGjmqLP6TWkfbliLeHq7EQ6ik3Bsf2 vozk5rLAbAvonfpzbu0JErT8+tQZPnzv8cHnqWlO7a/jio1nwsV9Hq6XI8WlEwg/lOtn a7jg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:references:in-reply-to:mime-version :arc-authentication-results; bh=GlrBmMoT0SpS0tCb3kfPNBWlcAub/1gQl+DZ6O28Uuo=; b=mhI05h8AVMVGLr0QjRWUvCGTY4hGcaaRHq6tV2istAjyc/pVUZZvOIdONcptbFCV8U jvwACEQhSpYqSohuGnHCPNRXyuS2elL/NnKxEieRyabzTIUk7n0yPWS8a4ffG7bhJV/w VfLWSl/kLNTgFtcDuv/meFhUOXypNh7ZB90XgKuVGGncvsMD8N75BGtvHQzqII8lXVpF UtfkC0XPEYGX3Cjid8LjA0IiUT+NrAtb6EFlqJEEnnJllwJ4UxRG23L497LROtTOde3X C0/pztNy33sZDLAhdc5O8rZBjqoncYo40fpiVrfmV2dNIAHv8qoQXtCgvpFFqb3OrRn3 jPhg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id o22si1178150pgv.232.2018.02.28.08.02.01; Wed, 28 Feb 2018 08:02:25 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932505AbeB1QBB convert rfc822-to-8bit (ORCPT + 99 others); Wed, 28 Feb 2018 11:01:01 -0500 Received: from mail-qt0-f195.google.com ([209.85.216.195]:39983 "EHLO mail-qt0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932207AbeB1QA7 (ORCPT ); Wed, 28 Feb 2018 11:00:59 -0500 Received: by mail-qt0-f195.google.com with SMTP id y6so3565523qtm.7 for ; Wed, 28 Feb 2018 08:00:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=Q6OWQ5K2PT6F0eWWaeJRUY4PlmeL5izaPVTkZQ2u87U=; b=MjCFj6RaSLiTfMkjbOjzwrvDNBiwv5XyAXeIP65Pzia7atXVYvI5CmhEkyuyIFC91+ IlQRdkyNdUOUHs5+Meqty62idAyCPvRwn6li6u+sTCU/rwoFWfvLGgjguuLN5qbiO/Fq g3HHG27SSYr5YoVtdLPUyt9HvAFMHX3VgmRJpDbuVs326LvcnE7pFPlgfw/9092ze1cV VlLdGmwaa+6pgtcFa+UNN58LdxsetT7JQIMyxOyj5K3NGtlILasIW/hnIQoNwImVUwbr eh4YVfGhBFKcXHBBKIbglW1v8IiABytpruXHG9klxnNGqlxmSKMXUOqxewISk8eSdv7L x5QA== X-Gm-Message-State: APf1xPClHTNsgKdjmXhcgjHjEqcTuzbeUr09VDOvdkUqNxbYkYpXJTfz CAX82YkOFsMpJxWFyjEE6m/Dvtt7dWydzZ95yBaQYg== X-Received: by 10.200.35.141 with SMTP id q13mr28639491qtq.73.1519833658602; Wed, 28 Feb 2018 08:00:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.12.137.194 with HTTP; Wed, 28 Feb 2018 08:00:58 -0800 (PST) In-Reply-To: <20180228174635-mutt-send-email-mst@kernel.org> References: <20180215213312.29234-1-marcandre.lureau@redhat.com> <20180215213312.29234-12-marcandre.lureau@redhat.com> <20180227020104-mutt-send-email-mst@kernel.org> <20180228173444-mutt-send-email-mst@kernel.org> <20180228174635-mutt-send-email-mst@kernel.org> From: =?UTF-8?B?TWFyYy1BbmRyw6kgTHVyZWF1?= Date: Wed, 28 Feb 2018 17:00:58 +0100 Message-ID: Subject: Re: [PATCH v15 11/11] RFC: fw_cfg: do DMA read operation To: "Michael S. Tsirkin" Cc: Linux Kernel Mailing List , Sergio Lopez Pascual , Baoquan He , "Somlo, Gabriel" , xiaolong.ye@intel.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi On Wed, Feb 28, 2018 at 4:48 PM, Michael S. Tsirkin wrote: > On Wed, Feb 28, 2018 at 04:41:51PM +0100, Marc-André Lureau wrote: >> I don't know if it's always safe to enable dma in read_raw(), how >> could we know? Is there a check we could use to choose one or ther >> other (and thus avoiding explicit dma/readfn argument)? > > I'm not sure - but does it really matter? Is anyone reading large files > like this in production where speed matters? > Why even bother with DMA? The difference is quite significante for not so small files, as shown above. And if they access the fw_cfg entries at boot time, or when starting things etc, this may speed things up.