From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751598AbeA3KmW (ORCPT ); Tue, 30 Jan 2018 05:42:22 -0500 Received: from mail-wm0-f51.google.com ([74.125.82.51]:35564 "EHLO mail-wm0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751366AbeA3KmU (ORCPT ); Tue, 30 Jan 2018 05:42:20 -0500 X-Google-Smtp-Source: AH8x226c3L7C604ZQ7i8Yh2/n2B0akZl9b/7RlaiPKct+PCIvg41Ip2h5HJtmSEfcYlkbcvcfop7og== Date: Tue, 30 Jan 2018 11:42:16 +0100 From: Daniel Vetter To: Michel =?iso-8859-1?Q?D=E4nzer?= Cc: christian.koenig@amd.com, Michal Hocko , dri-devel@lists.freedesktop.org, Roman Gushchin , linux-kernel@vger.kernel.org, linux-mm@kvack.org, amd-gfx@lists.freedesktop.org Subject: Re: [RFC] Per file OOM badness Message-ID: <20180130104216.GR25930@phenom.ffwll.local> Mail-Followup-To: Michel =?iso-8859-1?Q?D=E4nzer?= , christian.koenig@amd.com, Michal Hocko , dri-devel@lists.freedesktop.org, Roman Gushchin , linux-kernel@vger.kernel.org, linux-mm@kvack.org, amd-gfx@lists.freedesktop.org References: <20180123153631.GR1526@dhcp22.suse.cz> <20180124092847.GI1526@dhcp22.suse.cz> <583f328e-ff46-c6a4-8548-064259995766@daenzer.net> <20180124110141.GA28465@dhcp22.suse.cz> <36b49523-792d-45f9-8617-32b6d9d77418@daenzer.net> <20180124115059.GC28465@dhcp22.suse.cz> <381a868c-78fd-d0d1-029e-a2cf4ab06d37@gmail.com> <20180130093145.GE25930@phenom.ffwll.local> <3db43c1a-59b8-af86-2b87-c783c629f512@daenzer.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3db43c1a-59b8-af86-2b87-c783c629f512@daenzer.net> X-Operating-System: Linux phenom 4.14.0-1-amd64 User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 30, 2018 at 10:43:10AM +0100, Michel Dänzer wrote: > On 2018-01-30 10:31 AM, Daniel Vetter wrote: > > On Wed, Jan 24, 2018 at 01:11:09PM +0100, Christian König wrote: > >> Am 24.01.2018 um 12:50 schrieb Michal Hocko: > >>> On Wed 24-01-18 12:23:10, Michel Dänzer wrote: > >>>> On 2018-01-24 12:01 PM, Michal Hocko wrote: > >>>>> On Wed 24-01-18 11:27:15, Michel Dänzer wrote: > >>> [...] > >>>>>> 2. If the OOM killer kills a process which is sharing BOs with another > >>>>>> process, this should result in the other process dropping its references > >>>>>> to the BOs as well, at which point the memory is released. > >>>>> OK. How exactly are those BOs mapped to the userspace? > >>>> I'm not sure what you're asking. Userspace mostly uses a GEM handle to > >>>> refer to a BO. There can also be userspace CPU mappings of the BO's > >>>> memory, but userspace doesn't need CPU mappings for all BOs and only > >>>> creates them as needed. > >>> OK, I guess you have to bear with me some more. This whole stack is a > >>> complete uknonwn. I am mostly after finding a boundary where you can > >>> charge the allocated memory to the process so that the oom killer can > >>> consider it. Is there anything like that? Except for the proposed file > >>> handle hack? > >> > >> Not that I knew of. > >> > >> As I said before we need some kind of callback that a process now starts to > >> use a file descriptor, but without anything from that file descriptor mapped > >> into the address space. > > > > For more context: With DRI3 and wayland the compositor opens the DRM fd > > and then passes it to the client, which then starts allocating stuff. That > > makes book-keeping rather annoying. > > Actually, what you're describing is only true for the buffers shared by > an X server with an X11 compositor. For the actual applications, the > buffers are created on the client side and then shared with the X server > / Wayland compositor. > > Anyway, it doesn't really matter. In all cases, the buffers are actually > used by all parties that are sharing them, so charging the memory to all > of them is perfectly appropriate. > > > > I guess a good first order approximation would be if we simply charge any > > newly allocated buffers to the process that created them, but that means > > hanging onto lots of mm_struct pointers since we want to make sure we then > > release those pages to the right mm again (since the process that drops > > the last ref might be a totally different one, depending upon how the > > buffers or DRM fd have been shared). > > > > Would it be ok to hang onto potentially arbitrary mmget references > > essentially forever? If that's ok I think we can do your process based > > account (minus a few minor inaccuracies for shared stuff perhaps, but no > > one cares about that). > > Honestly, I think you and Christian are overthinking this. Let's try > charging the memory to every process which shares a buffer, and go from > there. I'm not concerned about wrongly accounting shared buffers (they don't matter), but imbalanced accounting. I.e. allocate a buffer in the client, share it, but then the compositor drops the last reference. If we store the mm_struct pointer in drm_gem_object, we don't need any callback from the vfs when fds are shared or anything like that. We can simply account any newly allocated buffers to the current->mm, and then store that later for dropping the account for when the gem obj is released. This would entirely ignore any complications with shared buffers, which I think we can do because even when we pass the DRM fd to a different process, the actual buffer allocations are not passed around like that for private buffers. And private buffers are the only ones that really matter. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f198.google.com (mail-wr0-f198.google.com [209.85.128.198]) by kanga.kvack.org (Postfix) with ESMTP id D8BAE6B0005 for ; Tue, 30 Jan 2018 05:42:20 -0500 (EST) Received: by mail-wr0-f198.google.com with SMTP id y44so3923482wry.8 for ; Tue, 30 Jan 2018 02:42:20 -0800 (PST) Received: from mail-sor-f41.google.com (mail-sor-f41.google.com. [209.85.220.41]) by mx.google.com with SMTPS id m31sor6996119edc.15.2018.01.30.02.42.19 for (Google Transport Security); Tue, 30 Jan 2018 02:42:19 -0800 (PST) Date: Tue, 30 Jan 2018 11:42:16 +0100 From: Daniel Vetter Subject: Re: [RFC] Per file OOM badness Message-ID: <20180130104216.GR25930@phenom.ffwll.local> References: <20180123153631.GR1526@dhcp22.suse.cz> <20180124092847.GI1526@dhcp22.suse.cz> <583f328e-ff46-c6a4-8548-064259995766@daenzer.net> <20180124110141.GA28465@dhcp22.suse.cz> <36b49523-792d-45f9-8617-32b6d9d77418@daenzer.net> <20180124115059.GC28465@dhcp22.suse.cz> <381a868c-78fd-d0d1-029e-a2cf4ab06d37@gmail.com> <20180130093145.GE25930@phenom.ffwll.local> <3db43c1a-59b8-af86-2b87-c783c629f512@daenzer.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3db43c1a-59b8-af86-2b87-c783c629f512@daenzer.net> Sender: owner-linux-mm@kvack.org List-ID: To: Michel =?iso-8859-1?Q?D=E4nzer?= Cc: christian.koenig@amd.com, Michal Hocko , dri-devel@lists.freedesktop.org, Roman Gushchin , linux-kernel@vger.kernel.org, linux-mm@kvack.org, amd-gfx@lists.freedesktop.org On Tue, Jan 30, 2018 at 10:43:10AM +0100, Michel Danzer wrote: > On 2018-01-30 10:31 AM, Daniel Vetter wrote: > > On Wed, Jan 24, 2018 at 01:11:09PM +0100, Christian Konig wrote: > >> Am 24.01.2018 um 12:50 schrieb Michal Hocko: > >>> On Wed 24-01-18 12:23:10, Michel Danzer wrote: > >>>> On 2018-01-24 12:01 PM, Michal Hocko wrote: > >>>>> On Wed 24-01-18 11:27:15, Michel Danzer wrote: > >>> [...] > >>>>>> 2. If the OOM killer kills a process which is sharing BOs with another > >>>>>> process, this should result in the other process dropping its references > >>>>>> to the BOs as well, at which point the memory is released. > >>>>> OK. How exactly are those BOs mapped to the userspace? > >>>> I'm not sure what you're asking. Userspace mostly uses a GEM handle to > >>>> refer to a BO. There can also be userspace CPU mappings of the BO's > >>>> memory, but userspace doesn't need CPU mappings for all BOs and only > >>>> creates them as needed. > >>> OK, I guess you have to bear with me some more. This whole stack is a > >>> complete uknonwn. I am mostly after finding a boundary where you can > >>> charge the allocated memory to the process so that the oom killer can > >>> consider it. Is there anything like that? Except for the proposed file > >>> handle hack? > >> > >> Not that I knew of. > >> > >> As I said before we need some kind of callback that a process now starts to > >> use a file descriptor, but without anything from that file descriptor mapped > >> into the address space. > > > > For more context: With DRI3 and wayland the compositor opens the DRM fd > > and then passes it to the client, which then starts allocating stuff. That > > makes book-keeping rather annoying. > > Actually, what you're describing is only true for the buffers shared by > an X server with an X11 compositor. For the actual applications, the > buffers are created on the client side and then shared with the X server > / Wayland compositor. > > Anyway, it doesn't really matter. In all cases, the buffers are actually > used by all parties that are sharing them, so charging the memory to all > of them is perfectly appropriate. > > > > I guess a good first order approximation would be if we simply charge any > > newly allocated buffers to the process that created them, but that means > > hanging onto lots of mm_struct pointers since we want to make sure we then > > release those pages to the right mm again (since the process that drops > > the last ref might be a totally different one, depending upon how the > > buffers or DRM fd have been shared). > > > > Would it be ok to hang onto potentially arbitrary mmget references > > essentially forever? If that's ok I think we can do your process based > > account (minus a few minor inaccuracies for shared stuff perhaps, but no > > one cares about that). > > Honestly, I think you and Christian are overthinking this. Let's try > charging the memory to every process which shares a buffer, and go from > there. I'm not concerned about wrongly accounting shared buffers (they don't matter), but imbalanced accounting. I.e. allocate a buffer in the client, share it, but then the compositor drops the last reference. If we store the mm_struct pointer in drm_gem_object, we don't need any callback from the vfs when fds are shared or anything like that. We can simply account any newly allocated buffers to the current->mm, and then store that later for dropping the account for when the gem obj is released. This would entirely ignore any complications with shared buffers, which I think we can do because even when we pass the DRM fd to a different process, the actual buffer allocations are not passed around like that for private buffers. And private buffers are the only ones that really matter. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Vetter Subject: Re: [RFC] Per file OOM badness Date: Tue, 30 Jan 2018 11:42:16 +0100 Message-ID: <20180130104216.GR25930@phenom.ffwll.local> References: <20180123153631.GR1526@dhcp22.suse.cz> <20180124092847.GI1526@dhcp22.suse.cz> <583f328e-ff46-c6a4-8548-064259995766@daenzer.net> <20180124110141.GA28465@dhcp22.suse.cz> <36b49523-792d-45f9-8617-32b6d9d77418@daenzer.net> <20180124115059.GC28465@dhcp22.suse.cz> <381a868c-78fd-d0d1-029e-a2cf4ab06d37@gmail.com> <20180130093145.GE25930@phenom.ffwll.local> <3db43c1a-59b8-af86-2b87-c783c629f512@daenzer.net> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Return-path: Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com [IPv6:2a00:1450:400c:c09::22e]) by gabe.freedesktop.org (Postfix) with ESMTPS id A187A6E92B for ; Tue, 30 Jan 2018 10:42:20 +0000 (UTC) Received: by mail-wm0-x22e.google.com with SMTP id 141so114975wme.3 for ; Tue, 30 Jan 2018 02:42:20 -0800 (PST) Content-Disposition: inline In-Reply-To: <3db43c1a-59b8-af86-2b87-c783c629f512@daenzer.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Michel =?iso-8859-1?Q?D=E4nzer?= Cc: linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, christian.koenig@amd.com, linux-mm@kvack.org, amd-gfx@lists.freedesktop.org, Michal Hocko , Roman Gushchin List-Id: dri-devel@lists.freedesktop.org T24gVHVlLCBKYW4gMzAsIDIwMTggYXQgMTA6NDM6MTBBTSArMDEwMCwgTWljaGVsIETDpG56ZXIg d3JvdGU6Cj4gT24gMjAxOC0wMS0zMCAxMDozMSBBTSwgRGFuaWVsIFZldHRlciB3cm90ZToKPiA+ IE9uIFdlZCwgSmFuIDI0LCAyMDE4IGF0IDAxOjExOjA5UE0gKzAxMDAsIENocmlzdGlhbiBLw7Zu aWcgd3JvdGU6Cj4gPj4gQW0gMjQuMDEuMjAxOCB1bSAxMjo1MCBzY2hyaWViIE1pY2hhbCBIb2Nr bzoKPiA+Pj4gT24gV2VkIDI0LTAxLTE4IDEyOjIzOjEwLCBNaWNoZWwgRMOkbnplciB3cm90ZToK PiA+Pj4+IE9uIDIwMTgtMDEtMjQgMTI6MDEgUE0sIE1pY2hhbCBIb2NrbyB3cm90ZToKPiA+Pj4+ PiBPbiBXZWQgMjQtMDEtMTggMTE6Mjc6MTUsIE1pY2hlbCBEw6RuemVyIHdyb3RlOgo+ID4+PiBb Li4uXQo+ID4+Pj4+PiAyLiBJZiB0aGUgT09NIGtpbGxlciBraWxscyBhIHByb2Nlc3Mgd2hpY2gg aXMgc2hhcmluZyBCT3Mgd2l0aCBhbm90aGVyCj4gPj4+Pj4+IHByb2Nlc3MsIHRoaXMgc2hvdWxk IHJlc3VsdCBpbiB0aGUgb3RoZXIgcHJvY2VzcyBkcm9wcGluZyBpdHMgcmVmZXJlbmNlcwo+ID4+ Pj4+PiB0byB0aGUgQk9zIGFzIHdlbGwsIGF0IHdoaWNoIHBvaW50IHRoZSBtZW1vcnkgaXMgcmVs ZWFzZWQuCj4gPj4+Pj4gT0suIEhvdyBleGFjdGx5IGFyZSB0aG9zZSBCT3MgbWFwcGVkIHRvIHRo ZSB1c2Vyc3BhY2U/Cj4gPj4+PiBJJ20gbm90IHN1cmUgd2hhdCB5b3UncmUgYXNraW5nLiBVc2Vy c3BhY2UgbW9zdGx5IHVzZXMgYSBHRU0gaGFuZGxlIHRvCj4gPj4+PiByZWZlciB0byBhIEJPLiBU aGVyZSBjYW4gYWxzbyBiZSB1c2Vyc3BhY2UgQ1BVIG1hcHBpbmdzIG9mIHRoZSBCTydzCj4gPj4+ PiBtZW1vcnksIGJ1dCB1c2Vyc3BhY2UgZG9lc24ndCBuZWVkIENQVSBtYXBwaW5ncyBmb3IgYWxs IEJPcyBhbmQgb25seQo+ID4+Pj4gY3JlYXRlcyB0aGVtIGFzIG5lZWRlZC4KPiA+Pj4gT0ssIEkg Z3Vlc3MgeW91IGhhdmUgdG8gYmVhciB3aXRoIG1lIHNvbWUgbW9yZS4gVGhpcyB3aG9sZSBzdGFj ayBpcyBhCj4gPj4+IGNvbXBsZXRlIHVrbm9ud24uIEkgYW0gbW9zdGx5IGFmdGVyIGZpbmRpbmcg YSBib3VuZGFyeSB3aGVyZSB5b3UgY2FuCj4gPj4+IGNoYXJnZSB0aGUgYWxsb2NhdGVkIG1lbW9y eSB0byB0aGUgcHJvY2VzcyBzbyB0aGF0IHRoZSBvb20ga2lsbGVyIGNhbgo+ID4+PiBjb25zaWRl ciBpdC4gSXMgdGhlcmUgYW55dGhpbmcgbGlrZSB0aGF0PyBFeGNlcHQgZm9yIHRoZSBwcm9wb3Nl ZCBmaWxlCj4gPj4+IGhhbmRsZSBoYWNrPwo+ID4+Cj4gPj4gTm90IHRoYXQgSSBrbmV3IG9mLgo+ ID4+Cj4gPj4gQXMgSSBzYWlkIGJlZm9yZSB3ZSBuZWVkIHNvbWUga2luZCBvZiBjYWxsYmFjayB0 aGF0IGEgcHJvY2VzcyBub3cgc3RhcnRzIHRvCj4gPj4gdXNlIGEgZmlsZSBkZXNjcmlwdG9yLCBi dXQgd2l0aG91dCBhbnl0aGluZyBmcm9tIHRoYXQgZmlsZSBkZXNjcmlwdG9yIG1hcHBlZAo+ID4+ IGludG8gdGhlIGFkZHJlc3Mgc3BhY2UuCj4gPiAKPiA+IEZvciBtb3JlIGNvbnRleHQ6IFdpdGgg RFJJMyBhbmQgd2F5bGFuZCB0aGUgY29tcG9zaXRvciBvcGVucyB0aGUgRFJNIGZkCj4gPiBhbmQg dGhlbiBwYXNzZXMgaXQgdG8gdGhlIGNsaWVudCwgd2hpY2ggdGhlbiBzdGFydHMgYWxsb2NhdGlu ZyBzdHVmZi4gVGhhdAo+ID4gbWFrZXMgYm9vay1rZWVwaW5nIHJhdGhlciBhbm5veWluZy4KPiAK PiBBY3R1YWxseSwgd2hhdCB5b3UncmUgZGVzY3JpYmluZyBpcyBvbmx5IHRydWUgZm9yIHRoZSBi dWZmZXJzIHNoYXJlZCBieQo+IGFuIFggc2VydmVyIHdpdGggYW4gWDExIGNvbXBvc2l0b3IuIEZv ciB0aGUgYWN0dWFsIGFwcGxpY2F0aW9ucywgdGhlCj4gYnVmZmVycyBhcmUgY3JlYXRlZCBvbiB0 aGUgY2xpZW50IHNpZGUgYW5kIHRoZW4gc2hhcmVkIHdpdGggdGhlIFggc2VydmVyCj4gLyBXYXls YW5kIGNvbXBvc2l0b3IuCj4gCj4gQW55d2F5LCBpdCBkb2Vzbid0IHJlYWxseSBtYXR0ZXIuIElu IGFsbCBjYXNlcywgdGhlIGJ1ZmZlcnMgYXJlIGFjdHVhbGx5Cj4gdXNlZCBieSBhbGwgcGFydGll cyB0aGF0IGFyZSBzaGFyaW5nIHRoZW0sIHNvIGNoYXJnaW5nIHRoZSBtZW1vcnkgdG8gYWxsCj4g b2YgdGhlbSBpcyBwZXJmZWN0bHkgYXBwcm9wcmlhdGUuCj4gCj4gCj4gPiBJIGd1ZXNzIGEgZ29v ZCBmaXJzdCBvcmRlciBhcHByb3hpbWF0aW9uIHdvdWxkIGJlIGlmIHdlIHNpbXBseSBjaGFyZ2Ug YW55Cj4gPiBuZXdseSBhbGxvY2F0ZWQgYnVmZmVycyB0byB0aGUgcHJvY2VzcyB0aGF0IGNyZWF0 ZWQgdGhlbSwgYnV0IHRoYXQgbWVhbnMKPiA+IGhhbmdpbmcgb250byBsb3RzIG9mIG1tX3N0cnVj dCBwb2ludGVycyBzaW5jZSB3ZSB3YW50IHRvIG1ha2Ugc3VyZSB3ZSB0aGVuCj4gPiByZWxlYXNl IHRob3NlIHBhZ2VzIHRvIHRoZSByaWdodCBtbSBhZ2FpbiAoc2luY2UgdGhlIHByb2Nlc3MgdGhh dCBkcm9wcwo+ID4gdGhlIGxhc3QgcmVmIG1pZ2h0IGJlIGEgdG90YWxseSBkaWZmZXJlbnQgb25l LCBkZXBlbmRpbmcgdXBvbiBob3cgdGhlCj4gPiBidWZmZXJzIG9yIERSTSBmZCBoYXZlIGJlZW4g c2hhcmVkKS4KPiA+IAo+ID4gV291bGQgaXQgYmUgb2sgdG8gaGFuZyBvbnRvIHBvdGVudGlhbGx5 IGFyYml0cmFyeSBtbWdldCByZWZlcmVuY2VzCj4gPiBlc3NlbnRpYWxseSBmb3JldmVyPyBJZiB0 aGF0J3Mgb2sgSSB0aGluayB3ZSBjYW4gZG8geW91ciBwcm9jZXNzIGJhc2VkCj4gPiBhY2NvdW50 IChtaW51cyBhIGZldyBtaW5vciBpbmFjY3VyYWNpZXMgZm9yIHNoYXJlZCBzdHVmZiBwZXJoYXBz LCBidXQgbm8KPiA+IG9uZSBjYXJlcyBhYm91dCB0aGF0KS4KPiAKPiBIb25lc3RseSwgSSB0aGlu ayB5b3UgYW5kIENocmlzdGlhbiBhcmUgb3ZlcnRoaW5raW5nIHRoaXMuIExldCdzIHRyeQo+IGNo YXJnaW5nIHRoZSBtZW1vcnkgdG8gZXZlcnkgcHJvY2VzcyB3aGljaCBzaGFyZXMgYSBidWZmZXIs IGFuZCBnbyBmcm9tCj4gdGhlcmUuCgpJJ20gbm90IGNvbmNlcm5lZCBhYm91dCB3cm9uZ2x5IGFj Y291bnRpbmcgc2hhcmVkIGJ1ZmZlcnMgKHRoZXkgZG9uJ3QKbWF0dGVyKSwgYnV0IGltYmFsYW5j ZWQgYWNjb3VudGluZy4gSS5lLiBhbGxvY2F0ZSBhIGJ1ZmZlciBpbiB0aGUgY2xpZW50LApzaGFy ZSBpdCwgYnV0IHRoZW4gdGhlIGNvbXBvc2l0b3IgZHJvcHMgdGhlIGxhc3QgcmVmZXJlbmNlLgoK SWYgd2Ugc3RvcmUgdGhlIG1tX3N0cnVjdCBwb2ludGVyIGluIGRybV9nZW1fb2JqZWN0LCB3ZSBk b24ndCBuZWVkIGFueQpjYWxsYmFjayBmcm9tIHRoZSB2ZnMgd2hlbiBmZHMgYXJlIHNoYXJlZCBv ciBhbnl0aGluZyBsaWtlIHRoYXQuIFdlIGNhbgpzaW1wbHkgYWNjb3VudCBhbnkgbmV3bHkgYWxs b2NhdGVkIGJ1ZmZlcnMgdG8gdGhlIGN1cnJlbnQtPm1tLCBhbmQgdGhlbgpzdG9yZSB0aGF0IGxh dGVyIGZvciBkcm9wcGluZyB0aGUgYWNjb3VudCBmb3Igd2hlbiB0aGUgZ2VtIG9iaiBpcwpyZWxl YXNlZC4gVGhpcyB3b3VsZCBlbnRpcmVseSBpZ25vcmUgYW55IGNvbXBsaWNhdGlvbnMgd2l0aCBz aGFyZWQKYnVmZmVycywgd2hpY2ggSSB0aGluayB3ZSBjYW4gZG8gYmVjYXVzZSBldmVuIHdoZW4g d2UgcGFzcyB0aGUgRFJNIGZkIHRvIGEKZGlmZmVyZW50IHByb2Nlc3MsIHRoZSBhY3R1YWwgYnVm ZmVyIGFsbG9jYXRpb25zIGFyZSBub3QgcGFzc2VkIGFyb3VuZApsaWtlIHRoYXQgZm9yIHByaXZh dGUgYnVmZmVycy4gQW5kIHByaXZhdGUgYnVmZmVycyBhcmUgdGhlIG9ubHkgb25lcyB0aGF0CnJl YWxseSBtYXR0ZXIuCi1EYW5pZWwKLS0gCkRhbmllbCBWZXR0ZXIKU29mdHdhcmUgRW5naW5lZXIs IEludGVsIENvcnBvcmF0aW9uCmh0dHA6Ly9ibG9nLmZmd2xsLmNoCl9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCmRyaS1kZXZlbCBtYWlsaW5nIGxpc3QKZHJp LWRldmVsQGxpc3RzLmZyZWVkZXNrdG9wLm9yZwpodHRwczovL2xpc3RzLmZyZWVkZXNrdG9wLm9y Zy9tYWlsbWFuL2xpc3RpbmZvL2RyaS1kZXZlbAo=