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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 13 Dec 2009 19:37:41 +0100
From:	Andi Kleen <>
To:	Stefani Seibold <>
Cc:	linux-kernel <>,
	Andrew Morton <>,
	Arnd Bergmann <>,
	Andi Kleen <>,
	Amerigo Wang <>,
	Joe Perches <>,
	Roger Quadros <>,
	Greg Kroah-Hartman <>,
	Mauro Carvalho Chehab <>,
	Shargorodsky Atal <>
Subject: Re: [PATCH 0/1] RFC: new kqueue API

On Sun, Dec 13, 2009 at 11:37:13AM +0100, Stefani Seibold wrote:
> As i figured out during the port the old kfifo API users, most of them
> did not need a streamed fifo, because there work only with fixed size
> entries. The kfifo is oversized for this kind of users, so i decided to
> write a new kqueue API which is optimized for fixed size entries. 
> There are a some benefits:
> - Performance (a put or get of an integer does only generate 4 assembly
> instructions on a x86) 
> - Type save
> - Cleaner interface
> - Easier to use
> - Less error prone
> - Smaller footprint
> The API is similar to the new kfifo API, but there is no need for a
> length paramter, because the size of the entry is know by the queue
> structure.

I must say I'm a bit sceptical if the advantages are really worth
the additional code. That code would be always compiled in in addition
to kfifo, so at least the code footprint would be always larger.

Perhaps you could get the advantages for type-safety using
inline wrappers to kfifo?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists