diff for duplicates of <1544177563.28511.34.camel@intel.com> diff --git a/a/1.txt b/N1/1.txt index c66b02c..869197e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,16 +1,21 @@ -T24gVGh1LCAyMDE4LTEyLTA2IGF0IDA2OjU5IC0wODAwLCBEYXZlIEhhbnNlbiB3cm90ZToNCj4g -T24gMTIvNi8xOCAzOjIyIEFNLCBLaXJpbGwgQS4gU2h1dGVtb3Ygd3JvdGU6DQo+ID4gPiBXaGVu -IHlvdSBzYXkgImRpc2FibGUgZW5jcnlwdGlvbiB0byBhIHBhZ2UiIGRvZXMgdGhlIGVuY3J5cHRp -b24gZ2V0DQo+ID4gPiBhY3R1YWxseSBkaXNhYmxlZCBvciBkb2VzIHRoZSBDUFUganVzdCBkZWNy -eXB0IGl0IHRyYW5zcGFyZW50bHkgaS5lLg0KPiA+ID4gd2hhdCBoYXBwZW5zIHBoeXNpY2FsbHk/ -DQo+ID4gDQo+ID4gWWVzLCBpdCBnZXRzIGRpc2FibGVkLiBQaHlzaWNhbGx5LiBJdCBvdmVycmlk -ZXMgVE1FIGVuY3J5cHRpb24uDQo+IA0KPiBJIGtub3cgTUtUTUUgaXRzZWxmIGhhcyBhIHJ1bnRp -bWUgb3ZlcmhlYWQgYW5kIHdlIGV4cGVjdCBpdCB0byBoYXZlIGENCj4gcGVyZm9ybWFuY2UgaW1w -YWN0IGluIHRoZSBsb3cgc2luZ2xlIGRpZ2l0cy4gIERvZXMgVE1FIGhhdmUgdGhhdA0KPiBvdmVy -aGVhZD8gIFByZXN1bWFibHkgTUtUTUUgcGx1cyBuby1lbmNyeXB0aW9uIGlzIG5vdCBleHBlY3Rl -ZCB0byBoYXZlDQo+IHRoZSBvdmVyaGVhZC4NCj4gDQo+IFdlIHNob3VsZCBwcm9iYWJseSBtZW50 -aW9uIHRoYXQgaW4gdGhlIGNoYW5nZWxvZ3MgdG9vLg0KPiANCg0KSSBiZWxpZXZlIGluIHRlcm1z -IG9mIGhhcmR3YXJlIGNyeXB0byBvdmVyaGVhZCBNS1RNRSBhbmQgVE1FIHNob3VsZCBoYXZlIHRo -ZSBzYW1lIChleGNlcHQgTUtUTUUgbm8tDQplbmNyeXB0IGNhc2U/KS4gQnV0IE1LVE1FIG1pZ2h0 -IGhhdmUgYWRkaXRpb25hbCBvdmVyaGVhZCBmcm9tIHNvZnR3YXJlIGltcGxlbWVudGF0aW9uIGlu -IGtlcm5lbD8NCg0KVGhhbmtzLA0KLUthaQ= +On Thu, 2018-12-06 at 06:59 -0800, Dave Hansen wrote: +> On 12/6/18 3:22 AM, Kirill A. Shutemov wrote: +> > > When you say "disable encryption to a page" does the encryption get +> > > actually disabled or does the CPU just decrypt it transparently i.e. +> > > what happens physically? +> > +> > Yes, it gets disabled. Physically. It overrides TME encryption. +> +> I know MKTME itself has a runtime overhead and we expect it to have a +> performance impact in the low single digits. Does TME have that +> overhead? Presumably MKTME plus no-encryption is not expected to have +> the overhead. +> +> We should probably mention that in the changelogs too. +> + +I believe in terms of hardware crypto overhead MKTME and TME should have the same (except MKTME no- +encrypt case?). But MKTME might have additional overhead from software implementation in kernel? + +Thanks, +-Kai diff --git a/a/content_digest b/N1/content_digest index 825a4a1..6b942f9 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,7 +6,7 @@ "ref\0a0a1e0d2-ef32-8378-5363-b730afc99c03@intel.com\0" "From\0Huang, Kai <kai.huang@intel.com>\0" "Subject\0Re: [RFC v2 00/13] Multi-Key Total Memory Encryption API (MKTME)\0" - "Date\0Fri, 07 Dec 2018 10:12:47 +0000\0" + "Date\0Fri, 7 Dec 2018 10:12:47 +0000\0" "To\0kirill@shutemov.name <kirill@shutemov.name>" Sakkinen Jarkko <jarkko.sakkinen@intel.com> @@ -33,21 +33,26 @@ " Jun <jun.nakajima@intel.com>\0" "\00:1\0" "b\0" - "T24gVGh1LCAyMDE4LTEyLTA2IGF0IDA2OjU5IC0wODAwLCBEYXZlIEhhbnNlbiB3cm90ZToNCj4g\n" - "T24gMTIvNi8xOCAzOjIyIEFNLCBLaXJpbGwgQS4gU2h1dGVtb3Ygd3JvdGU6DQo+ID4gPiBXaGVu\n" - "IHlvdSBzYXkgImRpc2FibGUgZW5jcnlwdGlvbiB0byBhIHBhZ2UiIGRvZXMgdGhlIGVuY3J5cHRp\n" - "b24gZ2V0DQo+ID4gPiBhY3R1YWxseSBkaXNhYmxlZCBvciBkb2VzIHRoZSBDUFUganVzdCBkZWNy\n" - "eXB0IGl0IHRyYW5zcGFyZW50bHkgaS5lLg0KPiA+ID4gd2hhdCBoYXBwZW5zIHBoeXNpY2FsbHk/\n" - "DQo+ID4gDQo+ID4gWWVzLCBpdCBnZXRzIGRpc2FibGVkLiBQaHlzaWNhbGx5LiBJdCBvdmVycmlk\n" - "ZXMgVE1FIGVuY3J5cHRpb24uDQo+IA0KPiBJIGtub3cgTUtUTUUgaXRzZWxmIGhhcyBhIHJ1bnRp\n" - "bWUgb3ZlcmhlYWQgYW5kIHdlIGV4cGVjdCBpdCB0byBoYXZlIGENCj4gcGVyZm9ybWFuY2UgaW1w\n" - "YWN0IGluIHRoZSBsb3cgc2luZ2xlIGRpZ2l0cy4gIERvZXMgVE1FIGhhdmUgdGhhdA0KPiBvdmVy\n" - "aGVhZD8gIFByZXN1bWFibHkgTUtUTUUgcGx1cyBuby1lbmNyeXB0aW9uIGlzIG5vdCBleHBlY3Rl\n" - "ZCB0byBoYXZlDQo+IHRoZSBvdmVyaGVhZC4NCj4gDQo+IFdlIHNob3VsZCBwcm9iYWJseSBtZW50\n" - "aW9uIHRoYXQgaW4gdGhlIGNoYW5nZWxvZ3MgdG9vLg0KPiANCg0KSSBiZWxpZXZlIGluIHRlcm1z\n" - "IG9mIGhhcmR3YXJlIGNyeXB0byBvdmVyaGVhZCBNS1RNRSBhbmQgVE1FIHNob3VsZCBoYXZlIHRo\n" - "ZSBzYW1lIChleGNlcHQgTUtUTUUgbm8tDQplbmNyeXB0IGNhc2U/KS4gQnV0IE1LVE1FIG1pZ2h0\n" - "IGhhdmUgYWRkaXRpb25hbCBvdmVyaGVhZCBmcm9tIHNvZnR3YXJlIGltcGxlbWVudGF0aW9uIGlu\n" - IGtlcm5lbD8NCg0KVGhhbmtzLA0KLUthaQ= + "On Thu, 2018-12-06 at 06:59 -0800, Dave Hansen wrote:\n" + "> On 12/6/18 3:22 AM, Kirill A. Shutemov wrote:\n" + "> > > When you say \"disable encryption to a page\" does the encryption get\n" + "> > > actually disabled or does the CPU just decrypt it transparently i.e.\n" + "> > > what happens physically?\n" + "> > \n" + "> > Yes, it gets disabled. Physically. It overrides TME encryption.\n" + "> \n" + "> I know MKTME itself has a runtime overhead and we expect it to have a\n" + "> performance impact in the low single digits. Does TME have that\n" + "> overhead? Presumably MKTME plus no-encryption is not expected to have\n" + "> the overhead.\n" + "> \n" + "> We should probably mention that in the changelogs too.\n" + "> \n" + "\n" + "I believe in terms of hardware crypto overhead MKTME and TME should have the same (except MKTME no-\n" + "encrypt case?). But MKTME might have additional overhead from software implementation in kernel?\n" + "\n" + "Thanks,\n" + -Kai -d70053c463174656f261ecab5edc926531921d114b46312dc7708b5ddbb3c41f +a346e41ac9a89c9311a76a0357ff87d886391a73cb8f9730e8b9aaee573ccb64
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.