public inbox for [email protected]
 help / color / mirror / Atom feed
From: Lukas Czerner <[email protected]>
To: Stefano Garzarella <[email protected]>
Cc: [email protected]
Subject: Re: A way to run liburing tests on emulated nvme in qemu
Date: Thu, 10 Sep 2020 10:10:37 +0200	[thread overview]
Message-ID: <20200910081037.j26hht5dbv4xw5hc@work> (raw)
In-Reply-To: <20200910073837.u4vypgrcku674n2o@steredhat>

On Thu, Sep 10, 2020 at 09:38:37AM +0200, Stefano Garzarella wrote:
> Hi Lukas,
> 
> On Wed, Sep 09, 2020 at 08:27:03PM +0200, Lukas Czerner wrote:
> > Hi,
> > 
> > because I didn't have an acces to a nvme HW I created a simple set of
> > scripts to help me run the liburing test suite on emulated nvme device
> > in qemu. This has also an advantage of being able to test it on different
> > architectures.
> > 
> > Here is a repository on gihub.
> > https://github.com/lczerner/qemu-test-iouring
> > 
> > I am attaching a README file to give you some sence of what it is.
> > 
> > It is still work in progress and only supports x86_64 and ppc64 at the
> > moment. It is very much Fedora centric as that's what I am using. But
> > maybe someone find some use for it. Of course I accept patches/PRs.
> 
> Cool! Thanks for sharing!
> 
> I had a look and I will definitely try it!

Great!

> 
> Just a note, maybe you can make configurable through config file also
> the number of CPU and amount of memory of the VM.

Yes, that's definitelly something that's missing. It is easy to add so
I'll do that today.

Thanks!
-Lukas


> 
> Thanks,
> Stefano
> 


      reply	other threads:[~2020-09-10  8:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 18:27 A way to run liburing tests on emulated nvme in qemu Lukas Czerner
2020-09-10  7:38 ` Stefano Garzarella
2020-09-10  8:10   ` Lukas Czerner [this message]

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=20200910081037.j26hht5dbv4xw5hc@work \
    [email protected] \
    [email protected] \
    [email protected] \
    /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