lkml.org 
[lkml]   [2019]   [Nov]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH v25 01/12] Linux Random Number Generator
Date
Am Samstag, 16. November 2019, 12:25:21 CET schrieb Thomas Gleixner:

Hi Thomas,

> On Sat, 16 Nov 2019, Stephan Müller wrote:
> > +/**
> > + * Hot code path - Callback for interrupt handler
> > + */
> > +void add_interrupt_randomness(int irq, int irq_flags)
> > +{
> > + lrng_time_process();
> > +
> > + if (!lrng_pool_highres_timer()) {
> > + struct pt_regs *regs = get_irq_regs();
> > + static atomic_t reg_idx = ATOMIC_INIT(0);
> > + u64 ip;
> > +
> > + lrng_pool_lfsr_u32(jiffies);
> > + lrng_pool_lfsr_u32(irq);
> > + lrng_pool_lfsr_u32(irq_flags);
> > +
> > + if (regs) {
> > + u32 *ptr = (u32 *)regs;
> > + int reg_ptr = atomic_add_return_relaxed(1, &reg_idx);
> > + size_t n = (sizeof(struct pt_regs) / sizeof(u32));
> > +
> > + ip = instruction_pointer(regs);
> > + lrng_pool_lfsr_u32(*(ptr + (reg_ptr % n)));
> > + } else
> > + ip = _RET_IP_;
> > +
> > + lrng_pool_lfsr_u32(ip >> 32);
> > + lrng_pool_lfsr_u32(ip);
> > + }
>
> Is there a way to avoid all that processing right in the interrupt hot
> path and just store the raw data for later processing?

The main code path is lrng_time_process(). This code is streamlined as you
already suggested: it is very lightweight to the interrupt handler. Compared
to the existing /dev/random implementation it is about 50% faster.

When measuring the lrng_time_process, it takes on one particular test system
on average about 65 cycles where on that very same system the
add_interrupt_randomness code path from the existing /dev/random takes on
average about 97 cycles.

The additional code you see in the add_interrupt_randomness is only executed
if lrng_pool_highres_timer is not set. This is not set if the LRNG does not
find a high-resolution time stamp, i.e. random_get_entropy() returns 0. As on
most architectures this is now set, this code path is not executed.

This additional code path serves as an emergency code to collect some data
that smells random and having entropy but not having really much.

It may be a bit more stremlined but since it is hardly used, I left it as it
is so far. Do you see the need to streamline it more at this time?

Thanks a lot.


Ciao
Stephan


\
 
 \ /
  Last update: 2019-11-17 11:33    [W:0.147 / U:1.772 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site