Linux block layer
 help / color / mirror / Atom feed
From: "Jürgen Groß" <jgross@suse.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: "Roger Pau Monné" <roger@xenproject.org>,
	"Jens Axboe" <axboe@kernel.dk>,
	xen-devel@lists.xenproject.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org
Subject: Re: [PATCH 0/3] xen-blkback: do some I/O statistics rework
Date: Thu, 12 Nov 2026 08:01:53 +0100	[thread overview]
Message-ID: <3a052d2c-8d14-4cb1-b6fd-277a6b0c8196@suse.com> (raw)
In-Reply-To: <7af69a18-fcd7-48f9-a9e4-c2ddc060755e@suse.com>


[-- Attachment #1.1: Type: text/plain, Size: 641 bytes --]

On 12.11.26 07:34, Jan Beulich wrote:
> On 11.11.2026 17:20, Juergen Gross wrote:
>> Some rework of the blkback statics data handling.
>>
>> Juergen Gross (3):
>>    xen-blkback: Remove statistics logging on console
>>    xen-blkback: move statistics data into sub-structure
>>    xen-blkback: make statistics data persistent across disconnect/connect
> Reviewed-by: Jan Beulich <jbeulich@suse.com>

Thanks.

> In the last patch a brief comment on the global stats instance may be
> worth, to indicate it's guarded by the rings lock.
> 
> Also, do I maybe get a Reported-by: on the last patch?
Yes to both. :-)


Juergen

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

      reply	other threads:[~2026-11-12  7:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 16:20 [PATCH 0/3] xen-blkback: do some I/O statistics rework Juergen Gross
2026-11-11 16:20 ` [PATCH 1/3] xen-blkback: Remove statistics logging on console Juergen Gross
2026-11-11 16:20 ` [PATCH 2/3] xen-blkback: move statistics data into sub-structure Juergen Gross
2026-11-11 16:20 ` [PATCH 3/3] xen-blkback: make statistics data persistent across disconnect/connect Juergen Gross
2026-11-12  6:34 ` [PATCH 0/3] xen-blkback: do some I/O statistics rework Jan Beulich
2026-11-12  7:01   ` Jürgen Groß [this message]

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=3a052d2c-8d14-4cb1-b6fd-277a6b0c8196@suse.com \
    --to=jgross@suse.com \
    --cc=axboe@kernel.dk \
    --cc=jbeulich@suse.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger@xenproject.org \
    --cc=xen-devel@lists.xenproject.org \
    /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