linux-kernel - Re: [PATCH 09/11] vt: update gen_ucs_width.py to produce more space efficient tables

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4rn89r00-8294-092o-1n35-opopo1273qnp@syhkavp.arg>
Date: Tue, 15 Apr 2025 15:16:50 -0400 (EDT)
From: Nicolas Pitre <nico@...xnic.net>
To: Jiri Slaby <jirislaby@...nel.org>
cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, 
    linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 09/11] vt: update gen_ucs_width.py to produce more space
 efficient tables

On Mon, 14 Apr 2025, Jiri Slaby wrote:

> On 10. 04. 25, 3:14, Nicolas Pitre wrote:
> > From: Nicolas Pitre <npitre@...libre.com>
> > 
> > Split table ranges into BMP (16-bit) and non-BMP (above 16-bit).
> > This reduces the corresponding text size by 20-25%.
> 
> I like this!
> 
> > -struct interval {{
> > +struct interval16 {{
> > +	uint16_t first;
> > +	uint16_t last;
> > +}};
> > +
> > +struct interval32 {{
> >    uint32_t first;
> >    uint32_t last;
> 
> Actually, why not to use u16 and u32, respectively?

No particular reason. The kernel uses both so I picked the one that made 
it easier for prototyping in user space. It is u16+u32 now.


Nicolas