public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Waiman Long <waiman.long@hp.com>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org,
	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: Tue, 31 Mar 2015 18:23:52 -0400	[thread overview]
Message-ID: <551B1E78.1040000@hp.com> (raw)
In-Reply-To: <551B1878.8000105@osg.samsung.com>

On 03/31/2015 05:58 PM, Shuah Khan wrote:
> On 03/31/2015 03:53 PM, Waiman Long wrote:
>> On 03/31/2015 03:21 PM, Shuah Khan wrote:
>>> On 03/31/2015 11:28 AM, Waiman Long wrote:
>>>> This patch is based on the code sent out by Peter Zijstra as part
>>>> of his queue spinlock patch to provide a hashing function with open
>>>> addressing.  The lfsr() function can be used to return a sequence of
>>>> numbers that cycle through all the bit patterns (2^n -1) of a given
>>>> bit width n except the value 0 in a somewhat random fashion depending
>>>> on the LFSR tap that is being used.
>>> Does this new test intended to test a new kernel feature? If so could
>>> you please include what it tests in the commit log. It isn't very clear
>>> to me what this test does?
>>>
>> This test is for checking the correctness of the lfsr.h header file. I
>> will clarify that in the commit log.
>>
>>>> This code should be a standalone patch and not part of a larger
>>>> patch series.  I have also modified and extended it and added some
>>>> testing code to verify the correctness of the taps that are being used.
>>> The above can be left out of the commit log.
>>>
>> Sure.
>>
>>>> Signed-off-by: Waiman Long<Waiman.Long@hp.com>
>>>> ---
>>>>    include/linux/lfsr.h                     |   84
>>>> ++++++++++++++++++++++++++++++
>>>>    tools/testing/selftests/lfsr/Makefile    |   11 ++++
>>>>    tools/testing/selftests/lfsr/test-lfsr.c |   70
>>>> +++++++++++++++++++++++++
>>>>    3 files changed, 165 insertions(+), 0 deletions(-)
>>>>    create mode 100644 include/linux/lfsr.h
>>>>    create mode 100644 tools/testing/selftests/lfsr/Makefile
>>>>    create mode 100644 tools/testing/selftests/lfsr/test-lfsr.c
>>> I don't see the test added to selftests/Makefile? Is it the intent
>>> to leave it out of default test run and install? If this test
>>> is intended to be part of selftests run and install, please add
>>> it to selftests Makefile and also add install target support.
>>> You can find good examples in linux-kselftest next branch.
>>> Please add a .gitignore for git to ignore the binaries built.
>>>
>>> thanks,
>>> -- Shuah
>>>
>>>
>> Yes, it is intended to be left out of the default selftest run and
>> install because the lfsr.h header is for kernel internal use and is not
>> accessible from any of the kernel syscall APIs.
>>
> Please add this to the commit log as well that it shouldn't be included
> in the default run and install. Also BUG_ON and BUILD_BUG_ON are used
> in this test. These are kernel defines, hope these are included somehow.
>
> -- Shuah
>

I will update the patch once I receive feedbacks from others. The lfsr.h 
header does use BUG_ON and BUILD_BUG_ON, but they are disabled in the 
self-test.

-Longman

  reply	other threads:[~2015-03-31 22:23 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 [this message]
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
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=551B1E78.1040000@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox