From: Thomas Monjalon <thomas.monjalon@6wind.com>
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
Date: Wed, 26 Oct 2016 18:59:52 +0200 [thread overview]
Message-ID: <2132814.l4S2MXKORn@xps13> (raw)
In-Reply-To: <348A99DA5F5B7549AA880327E580B435891157AC@IRSMSX101.ger.corp.intel.com>
2016-10-26 16:50, Trahe, Fiona:
> Hi Thomas,
>
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > 2016-10-26 16:20, Fiona Trahe:
> > > add more info re VT-d/iommu settings for QAT remove limitation re
> > > performance tuning
> >
> > Sorry, I do not understand what means "re".
>
> "re" is commonly used in the English language and means "in reference to" or "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 'about', as in I saw the deputy head re the incident. However, the evidence suggests 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 compelling logical argument against using it as an ordinary English word in this way
Thanks for the detailed explanations, and sorry again for my ignorance :)
next prev parent reply other threads:[~2016-10-26 16:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 15:20 Fiona Trahe
2016-10-26 15:27 ` Thomas Monjalon
2016-10-26 16:50 ` Trahe, Fiona
2016-10-26 16:59 ` Thomas Monjalon [this message]
2016-10-26 17:23 ` [dpdk-dev] [PATCH v2] doc/guides: add more info about VT-d/iommu settings Fiona Trahe
2016-11-02 13:00 ` Kusztal, ArkadiuszX
2016-11-07 21:04 ` Thomas Monjalon
2016-10-26 17:38 ` [dpdk-dev] [PATCH] doc/guides: add more info re VT-d/iommu settings for QAT Jain, Deepak K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2132814.l4S2MXKORn@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).