From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Daniel Vetter <daniel@ffwll.ch>,
netdev@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Chris Wilson <chris@chris-wilson.co.uk>,
dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
David Airlie <airlied@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [Intel-gfx] [PATCH v7 0/7] drm/i915: use ref_tracker library for tracking wakerefs
Date: Fri, 21 Apr 2023 07:09:05 -0700 [thread overview]
Message-ID: <20230421070905.3ed2bb78@kernel.org> (raw)
In-Reply-To: <20230224-track_gt-v7-0-11f08358c1ec@intel.com>
On Fri, 21 Apr 2023 13:35:04 +0200 Andrzej Hajda wrote:
> Gently ping for network developers, could you look at ref_tracker patches,
> as the ref_tracker library was developed for network.
Putting Eric in the To: field, I know email so hard and confusing...
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Andi Shyti <andi.shyti@linux.intel.com>,
netdev@vger.kernel.org, intel-gfx@lists.freedesktop.org,
linux-kernel@vger.kernel.org,
Chris Wilson <chris@chris-wilson.co.uk>,
dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH v7 0/7] drm/i915: use ref_tracker library for tracking wakerefs
Date: Fri, 21 Apr 2023 07:09:05 -0700 [thread overview]
Message-ID: <20230421070905.3ed2bb78@kernel.org> (raw)
In-Reply-To: <20230224-track_gt-v7-0-11f08358c1ec@intel.com>
On Fri, 21 Apr 2023 13:35:04 +0200 Andrzej Hajda wrote:
> Gently ping for network developers, could you look at ref_tracker patches,
> as the ref_tracker library was developed for network.
Putting Eric in the To: field, I know email so hard and confusing...
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Eric Dumazet <edumazet@google.com>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Jani Nikula <jani.nikula@linux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
linux-kernel@vger.kernel.org, intel-gfx@lists.freedesktop.org,
dri-devel@lists.freedesktop.org,
Chris Wilson <chris@chris-wilson.co.uk>,
netdev@vger.kernel.org, Dmitry Vyukov <dvyukov@google.com>,
"David S. Miller" <davem@davemloft.net>,
Andi Shyti <andi.shyti@linux.intel.com>
Subject: Re: [PATCH v7 0/7] drm/i915: use ref_tracker library for tracking wakerefs
Date: Fri, 21 Apr 2023 07:09:05 -0700 [thread overview]
Message-ID: <20230421070905.3ed2bb78@kernel.org> (raw)
In-Reply-To: <20230224-track_gt-v7-0-11f08358c1ec@intel.com>
On Fri, 21 Apr 2023 13:35:04 +0200 Andrzej Hajda wrote:
> Gently ping for network developers, could you look at ref_tracker patches,
> as the ref_tracker library was developed for network.
Putting Eric in the To: field, I know email so hard and confusing...
next prev parent reply other threads:[~2023-04-21 14:10 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 11:35 [Intel-gfx] [PATCH v7 0/7] drm/i915: use ref_tracker library for tracking wakerefs Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 1/7] lib/ref_tracker: add unlocked leak print helper Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 14:24 ` [Intel-gfx] " Eric Dumazet
2023-04-21 14:24 ` Eric Dumazet
2023-04-21 14:24 ` Eric Dumazet
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 2/7] lib/ref_tracker: improve printing stats Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 14:21 ` [Intel-gfx] " Eric Dumazet
2023-04-21 14:21 ` Eric Dumazet
2023-04-21 14:21 ` Eric Dumazet
2023-04-21 14:30 ` [Intel-gfx] " Andrzej Hajda
2023-04-21 14:30 ` Andrzej Hajda
2023-04-21 14:30 ` Andrzej Hajda
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 3/7] lib/ref_tracker: add printing to memory buffer Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 4/7] lib/ref_tracker: remove warnings in case of allocation failure Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 14:21 ` [Intel-gfx] " Eric Dumazet
2023-04-21 14:21 ` Eric Dumazet
2023-04-21 14:21 ` Eric Dumazet
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 5/7] drm/i915: Correct type of wakeref variable Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 6/7] drm/i915: Replace custom intel runtime_pm tracker with ref_tracker library Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-23 4:45 ` [Intel-gfx] " Zhou Furong
2023-04-23 4:45 ` Zhou Furong
2023-04-23 4:45 ` Zhou Furong
2023-04-21 11:35 ` [Intel-gfx] [PATCH v7 7/7] drm/i915: track gt pm wakerefs Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-21 11:35 ` Andrzej Hajda
2023-04-23 3:53 ` [Intel-gfx] " Zhou Furong
2023-04-23 3:53 ` Zhou Furong
2023-04-23 3:53 ` Zhou Furong
2023-04-21 12:56 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: use ref_tracker library for tracking wakerefs (rev8) Patchwork
2023-04-21 12:56 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2023-04-21 13:16 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-21 14:09 ` Jakub Kicinski [this message]
2023-04-21 14:09 ` [PATCH v7 0/7] drm/i915: use ref_tracker library for tracking wakerefs Jakub Kicinski
2023-04-21 14:09 ` Jakub Kicinski
2023-04-21 20:57 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: use ref_tracker library for tracking wakerefs (rev8) Patchwork
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=20230421070905.3ed2bb78@kernel.org \
--to=kuba@kernel.org \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=daniel@ffwll.ch \
--cc=davem@davemloft.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=dvyukov@google.com \
--cc=edumazet@google.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rodrigo.vivi@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 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.