From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Petr Mladek <pmladek@suse.com>,
Steven Rostedt <rostedt@goodmis.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jonathan Corbet <corbet@lwn.net>,
John Ogness <john.ogness@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] hexdump: Allow skipping identical lines
Date: Mon, 13 Jan 2025 14:35:41 +0200 [thread overview]
Message-ID: <Z4UInSRCSXzNN5Ug@smile.fi.intel.com> (raw)
In-Reply-To: <20250110-perso-hexdump-v2-2-7f9a6a799170@bootlin.com>
On Fri, Jan 10, 2025 at 07:42:05PM +0100, Miquel Raynal wrote:
> When dumping long buffers (especially for debug purposes) it may be very
> convenient to sometimes avoid spitting all the lines of the buffer if
> the lines are identical. Typically on embedded devices, the console
> would be wired to a UART running at 115200 bauds, which makes the dumps
> very (very) slow. In this case, having a flag to avoid printing
> duplicated lines is handy.
>
> Example of a made up repetitive output:
> 0f 53 63 47 56 55 78 7a aa b7 8c ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff 01 2a 39 eb
>
> Same but with the flag enabled:
> 0f 53 63 47 56 55 78 7a aa b7 8c ff ff ff ff ff
> ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
> *
> ff ff ff ff ff ff ff ff ff ff ff ff 01 2a 39 eb
Still thinking that it's not okay to leave the cases where hex_dump_to_buffer()
is being used for the similar. I would expect that to be modified as well.
As told in v1 thread this can be achieved using a context data, instead of
providing zillion fields, one of which may be a kind of CRC32 checksum that
makes this work without any additional allocation.
But I won't prevent you to go with this if you get a blessing from other
PRINTK/PRINTF maintainers/reviewers.
...
> #include <linux/types.h>
> +#include <linux/string.h>
Can we keep it ordered (to some extent)? I know that types.h is misplaced here.
> #include <linux/ctype.h>
> #include <linux/errno.h>
> #include <linux/kernel.h>
...
> + if (flags & DUMP_FLAG_SKIP_IDENTICAL_LINES) {
> + if (i && !memcmp(ptr + i, ptr + prev_i, linelen)) {
> + prev_i = i;
Can we rather use a hash function or so instead of memcmp()?
> + if (same_line)
> + continue;
> + same_line = true;
> + printk("%s*\n", level);
> + continue;
> + } else {
Redundant 'else'.
> + prev_i = i;
> + same_line = false;
> + }
> + }
Something like
unsigned long hcur, hprev = ~0; // any unrealistic init value
...
if (flags & DUMP_FLAG_SKIP_IDENTICAL_LINES) {
hcur = $HASH($LINE);
if (hcur == hprev) {
...
continue;
}
hprev = hcur;
}
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-01-13 12:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 18:42 [PATCH v2 0/2] hexdump: Allow skipping identical lines Miquel Raynal
2025-01-10 18:42 ` [PATCH v2 1/2] hexdump: Convert the ascii boolean into a flag variable Miquel Raynal
2025-01-10 18:42 ` [PATCH v2 2/2] hexdump: Allow skipping identical lines Miquel Raynal
2025-01-10 19:39 ` David Laight
2025-01-11 9:54 ` Miquel Raynal
2025-01-11 12:10 ` David Laight
2025-01-13 10:04 ` Andy Shevchenko
2025-01-11 5:36 ` Randy Dunlap
2025-01-13 12:35 ` Andy Shevchenko [this message]
2025-01-17 16:27 ` Petr Mladek
2025-01-17 19:25 ` David Laight
2025-01-20 9:29 ` Miquel Raynal
2025-01-20 10:25 ` Petr Mladek
2025-01-13 12:40 ` [PATCH v2 0/2] " Andy Shevchenko
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=Z4UInSRCSXzNN5Ug@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=john.ogness@linutronix.de \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=miquel.raynal@bootlin.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).