From: Waiman Long <waiman.long@hp.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Shuah Khan <shuahkh@osg.samsung.com>,
Scott J Norton <scott.norton@hp.com>,
Douglas Hatch <doug.hatch@hp.com>
Subject: Re: [PATCH] lfsr: a simple binary Galois linear feedback shift register
Date: Wed, 01 Apr 2015 10:15:59 -0400 [thread overview]
Message-ID: <551BFD9F.2030403@hp.com> (raw)
In-Reply-To: <20150401075325.GV27490@worktop.programming.kicks-ass.net>
On 04/01/2015 03:53 AM, Peter Zijlstra wrote:
> On Tue, Mar 31, 2015 at 01:28:09PM -0400, Waiman Long wrote:
>> +static __always_inline u32 lfsr_taps(int bits)
>> +static inline u32 lfsr(u32 val, int bits)
>> +{
>> + u32 bit = val& 1;
>> +
>> + /*
>> + * LFSR doesn't work with a start state of 0, so force it to a
>> + * non-zero value (bits) as the next state.
>> + */
>> + if (val == 0)
>> + return bits;
> Arguably this should be a debug/warn instead of a silent modification.
Since it is used in conjunction with hashing, it is possible that
hashing can produce a value of 0. Do we really want to have a warning
for that? Alternatively, we can pass in some flag to decide if a warning
should be issued.
>> + val>>= 1;
>> + if (bit)
>> + val ^= lfsr_taps(bits);
>> + return val;
>> +}
> I was also thinking that if we modify the hash to be dynamically signed
> we cannot use the compile time tap selection and need to change the
> interface slightly.
So you mean having another argument for the caller to pass in the tap
value instead of using the default. Right?
-Longman
next prev parent reply other threads:[~2015-04-01 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 17:28 [PATCH] lfsr: a simple binary Galois linear feedback shift register Waiman Long
2015-03-31 19:21 ` Shuah Khan
2015-03-31 21:53 ` Waiman Long
2015-03-31 21:58 ` Shuah Khan
2015-03-31 22:23 ` Waiman Long
2015-04-01 7:45 ` Peter Zijlstra
2015-04-01 14:08 ` Waiman Long
2015-04-01 7:53 ` Peter Zijlstra
2015-04-01 14:15 ` Waiman Long [this message]
2015-04-01 16:46 ` Peter Zijlstra
2015-04-01 18:46 ` Peter Zijlstra
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=551BFD9F.2030403@hp.com \
--to=waiman.long@hp.com \
--cc=doug.hatch@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=scott.norton@hp.com \
--cc=shuahkh@osg.samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.