On Mon, May 21, 2018 at 8:31 AM, Udit agarwal <dev.mada...@gmail.com> wrote:
> Hi Gedare, Hi Joel, > > On Mon, May 21, 2018 at 6:53 PM, Gedare Bloom <ged...@rtems.org> wrote: > >> "License type customized" is not clear to me what that means, it would >> be worth explaining >> >> > In case of IOZONE's license > <http://www.iozone.org/docs/Iozone_License.txt>, by customized license > type, I just mean that it's not one of standard OSS licenses like GPL, BSD > etc. > I call this an "AS IS vendor" license but apparently, OSI gives something similar the name Free Public License 1.0.0 https://opensource.org/licenses/FPL-1.0.0 The IOZONE license meets the permissive license requirements for RTEMS. But again, we could just end up putting a disk_benchmarks directory under the RSB (or examples-v2[1]) and include instructions, RTEMS configuration, plus patches. I suspect that we will have to consider that an end user will have to customize the startup to account for device names, mounting, etc. That leaves the RSB a less than ideal situation unless we can figure out how to kit each benchmark properly. Overall, I am torn on where this code will end up but think it needs to be public from rtems.org, with easy tailoring and good instructions. [1] We need to eventually rename this to rtems-examples. :) > BTW, My domain name's DNS is currently misconfigured, website can be > accessed from here <http://81.4.107.225/wordpress/>. And for backup, I > have exported the > wordpress content to blogger(here <http://nerdyclap.blogspot.in/>). > (There are some alignment issues after exporting, mainly due to the custom > CSS i was using, i'll fix that ASAP) > > OK. Just pointing it out. :) --joel > Regards, > Udit Agarwal > > On Sun, May 20, 2018 at 7:32 PM, Joel Sherrill <j...@rtems.org> wrote: >> > >> > >> > On Sat, May 19, 2018, 5:06 PM Udit agarwal <dev.mada...@gmail.com> >> wrote: >> >> >> >> Hi, >> >> >> >> On Fri, May 18, 2018 at 11:19 PM, Gedare Bloom <ged...@rtems.org> >> wrote: >> >>> >> >>> Udit, >> >>> >> >>> Can you please compare pros/cons of FIO, IOZONE, and Bonnie++, >> >>> probably in a blog post is a good idea. >> >> >> >> Done, here is the comparison. >> > >> > >> > That url has a hard-coded IP address in it. GSoC blogs should be hosted >> > somewhere where they will have a long life with stable URLs. >> > >> > It looks nice though. :) >> > >> >>> >> >>> The GPLv2 is not a problem for test suites / benchmarks. It is only a >> >>> problem for code that should get merged into the rtems.git. >> >>> >> >>> Gedare >> >>> >> >>> On Thu, May 17, 2018 at 5:20 AM, Udit agarwal <dev.mada...@gmail.com> >> >>> wrote: >> >>> > Hi all, >> >>> > As discussed in yesterday's IRC meeting, here is the list of >> different >> >>> > IO >> >>> > benchmarks(which are supported by FreeBSD) in the decreasing order >> of >> >>> > their >> >>> > popularity : >> >>> > >> >>> > FIO - License type: GPLv2 - Widely accepted for storage device >> >>> > benchmarking >> >>> > IOZONE - License: Customized - Large number of features, Also used >> for >> >>> > storage benchmarking >> >>> > Bonnie++ - GPLv2 - Widely known filesystem benchmark, Not much used >> for >> >>> > storage benchmarking. >> >>> > IOMETER - GPLv2 - Out of active development. >> >>> > IORATE - Flexible - Out of active development >> >>> > >> >>> > I have performed SDIO-SDHCI performance analysis using IOZONE. Here >> are >> >>> > the >> >>> > results. And i have documented the process on my blog. >> >>> > >> >>> > Regards, >> >>> > >> >>> > Udit Agarwal >> >>> > >> >>> > >> >>> > _______________________________________________ >> >>> > devel mailing list >> >>> > devel@rtems.org >> >>> > http://lists.rtems.org/mailman/listinfo/devel >> >> >> >> >> >> _______________________________________________ >> >> devel mailing list >> >> devel@rtems.org >> >> http://lists.rtems.org/mailman/listinfo/devel >> > >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
