Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Alex Pyrgiotis <apyrgio@grnet.gr>
Cc: fio@vger.kernel.org, synnefo-devel@googlegroups.com
Subject: Re: [PATCH 0/2] Proposed LFSR implementation
Date: Mon, 11 Mar 2013 12:27:24 +0100	[thread overview]
Message-ID: <20130311112724.GW14525@kernel.dk> (raw)
In-Reply-To: <1362746224-5162-1-git-send-email-apyrgio@grnet.gr>

On Fri, Mar 08 2013, Alex Pyrgiotis wrote:
> Hi Jens and list,
> 
> Due to the open-source nature of fio, I figured I'd share with you
> something I've created while working on Archipelago[1], a storage
> backend for synnefo[2] VMs.
> 
> We wanted to have an entity that can do random permutations fast, so
> we've created an XNOR Galois LFSR (more details about the implementation
> in the following patches) that should perform "better" than the generic
> one for I/O related tasks.
> 
> By "better", I don't mean only in terms of speed - since by definition
> LFSRs are insanely fast - but also in terms of their properties as
> PRNGs. The main issue with LFSRs that can't make them a serious
> candidate for I/O tasks is that due to their shifting nature, they
> cannot produce a sequence of numbers that differs widely from one to the
> next. This implementation should tackle this problem and should make
> LFSRs promising candidates at least for randrepeat jobs.
> 
> I actually went one step further and tested this implementation against
> the TESTU01 suite. A generic LFSR fails all the tests as expected, but
> this LFSR passes 3 to 5 out the 10 entry level tests of the suite. This
> shows that they are far from suitable as stand-alone PRNGs for
> cryptography, but should be pretty decent for I/O tasks.
> 
> Anyways, hopefully you will find this patch set interesting for
> inclusion in your code. If you have any questions, feel free to ask.

This is good stuff! It is indeed far superior to the existing lfsr
implementation. I'll get this queued up for inclusion. Thanks a lot.

-- 
Jens Axboe


  parent reply	other threads:[~2013-03-11 11:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-08 12:37 [PATCH 0/2] Proposed LFSR implementation Alex Pyrgiotis
2013-03-08 12:37 ` [PATCH 1/2] Improve " Alex Pyrgiotis
2013-03-08 12:37 ` [PATCH 2/2] Add a simple test for LFSR generator Alex Pyrgiotis
2013-03-11 15:51   ` Jiri Horky
2013-03-12  6:45     ` Alex Pyrgiotis
2013-03-11 11:27 ` Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-03-08 18:30 [PATCH 0/2] Proposed LFSR implementation Alex Pyrgiotis

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=20130311112724.GW14525@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=apyrgio@grnet.gr \
    --cc=fio@vger.kernel.org \
    --cc=synnefo-devel@googlegroups.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