public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Ilvokhin <d@ilvokhin.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2] x86/irq: Optimize interrupts decimals printing
Date: Fri, 27 Feb 2026 14:04:01 +0000	[thread overview]
Message-ID: <aaGkUXrxzClRCqPy@shell.ilvokhin.com> (raw)
In-Reply-To: <87ms0uz5ja.ffs@tglx>

On Fri, Feb 27, 2026 at 02:20:57PM +0100, Thomas Gleixner wrote:
> On Wed, Feb 25 2026 at 17:22, Dmitry Ilvokhin wrote:
> 
> Sorry, this fell through the cracks.
> 
> > I would like to follow up on this patch with additional data from production
> > deployment.
> 
> Instead of the non-interesting advertising blurb, you could have had the
> courtesy to follow up with a new version of this patch after checking
> whether it still applies, which it does not.
> 
> But please spare the effort because I already fixed it up locally and
> thereby looked at the larger picture of /proc/interrupts.
> 
> It's amazing that all the people who "improve" that stuff never see the
> obvious low hanging fruit there. I'll send out a series later.

Hi Thomas,

Thanks for taking a look and for fixing it up locally.

I apologize for not checking whether the patch still applied before
following up, that was my mistake.

I'm glad to hear you're looking at the larger picture of
/proc/interrupts. If there’s anything I can help with (testing,
benchmarking, etc.), I'd be happy to assist.

> 
> Thanks,
> 
>         tglx
> 

      reply	other threads:[~2026-02-27 14:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 18:51 [PATCH v2] x86/irq: Optimize interrupts decimals printing Dmitry Ilvokhin
2026-02-25 17:22 ` Dmitry Ilvokhin
2026-02-27 13:20   ` Thomas Gleixner
2026-02-27 14:04     ` Dmitry Ilvokhin [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=aaGkUXrxzClRCqPy@shell.ilvokhin.com \
    --to=d@ilvokhin.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.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