From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <fiona.trahe@intel.com> Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 2F37CBD5B for <dev@dpdk.org>; Wed, 26 Oct 2016 18:50:22 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP; 26 Oct 2016 09:50:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,551,1473145200"; d="scan'208";a="1076134810" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by fmsmga002.fm.intel.com with ESMTP; 26 Oct 2016 09:50:20 -0700 Received: from irsmsx111.ger.corp.intel.com (10.108.20.4) by IRSMSX108.ger.corp.intel.com (163.33.3.3) with Microsoft SMTP Server (TLS) id 14.3.248.2; Wed, 26 Oct 2016 17:50:19 +0100 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.233]) by irsmsx111.ger.corp.intel.com ([10.108.20.4]) with mapi id 14.03.0248.002; Wed, 26 Oct 2016 17:50:19 +0100 From: "Trahe, Fiona" <fiona.trahe@intel.com> To: Thomas Monjalon <thomas.monjalon@6wind.com> Thread-Topic: [dpdk-dev] [PATCH] doc/guides: add more info re VT-d/iommu settings for QAT Thread-Index: AQHSL5yJHusbhJZlGEKxRvdhFA+qPqC6yvCAgAAlOEA= Date: Wed, 26 Oct 2016 16:50:17 +0000 Message-ID: <348A99DA5F5B7549AA880327E580B435891157AC@IRSMSX101.ger.corp.intel.com> References: <1477495224-2235-1-git-send-email-fiona.trahe@intel.com> <1620839.dXv2gATAhT@xps13> In-Reply-To: <1620839.dXv2gATAhT@xps13> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiOGQ2OWJkODgtMzIwNC00YmYwLTk5MzItMDlkODg0MWIyYjg5IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IkFCYTM1MTRFUjFlV3VtTDBXWVZYVVAyRzRNczRVYzQyQzBubEFscTJ6aUU9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" <dev@dpdk.org> Subject: Re: [dpdk-dev] [PATCH] doc/guides: add more info re VT-d/iommu settings for QAT X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 26 Oct 2016 16:50:22 -0000 Hi Thomas, > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Wednesday, October 26, 2016 4:27 PM > To: Trahe, Fiona <fiona.trahe@intel.com> > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH] doc/guides: add more info re VT-d/iommu > settings for QAT >=20 > 2016-10-26 16:20, Fiona Trahe: > > add more info re VT-d/iommu settings for QAT remove limitation re > > performance tuning >=20 > Sorry, I do not understand what means "re". "re" is commonly used in the English language and means "in reference to" o= r "about" but I'm happy to change to "about" which is the more conventional word. There's an interesting explanation of the evolution of the term here: https://en.oxforddictionaries.com/definition/re Usage The traditional view is that re should be used in headings and references, = as in Re: Ainsworth versus Chambers, but not as a normal word meaning 'abou= t', as in I saw the deputy head re the incident. However, the evidence sugg= ests that re is now widely used in the second context in official and semi-= official contexts, and is now generally accepted. It is hard to see any com= pelling logical argument against using it as an ordinary English word in th= is way > Please use an uppercase at the beginning of each sentence and a dot at th= e > end. It helps reading. Ok. =20 I was confusing this with the style needed for the email subject, which is = the opposite!