From: Paulina Szubarczyk <paulinaszubarczyk@gmail.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org,
Dario Faggioli <dario.faggioli@citrix.com>,
Mina Naghshnejad <mina.naghshnejad@gmail.com>
Subject: Re: Outreachy bite-sized tasks
Date: Fri, 1 Apr 2016 12:05:42 +0200 [thread overview]
Message-ID: <CAMQpU2rsaSNMCJeyzAWNgL_PW4HrD8LthkcVspH9jSayWwKTTA@mail.gmail.com> (raw)
In-Reply-To: <1458757308.5082.7.camel@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 2200 bytes --]
Hi Roger,
An another point that needs to be filled up in the application is timeline.
I made the proposition of it, I am not sure if it should be more complex.
Could you look at it in your free time?
Timeline:
22 April - 22 May [Before the intership]
* Elaborate performance measurement methodology. That may include putting
trace
points using TRDCS and performing read operation with varying
block sizes on
different storage devices as in [3].
* Gain a profound knowledge about implementation of xen-blkback in
Qemu and Linux kernel.
23 May - 6 June [Begin of the intership - up to two weeks]
* Prepare and improve performance measurement test.
* Gather and document the results.
6 June - 23 August
* Base on the analysis and the task description implement performance
improvement future
inside of QEMU's xen-blkback.
* Prepare and run regression tests and continue performance measurement
for
each implemented feature.
* Document the results.
15 August - 23 August [Close to the end]
* Sum up the work:
- indicate the obstacles
- form the conclusion and
- indicate future work.
References:
[1] http://lxr.free-electrons.com/source/drivers/block/xen-blkback/blkback.c
[2]
http://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/include/public/io/blkif.h
[3]
https://events.linuxfoundation.org/sites/events/files/slides/20131025%20-%20Storage%20Performance%20PDF.pdf
On 23 March 2016 at 19:21, Dario Faggioli <dario.faggioli@citrix.com> wrote:
> Hey,
>
> please, do not use HTML for emails to this list.
>
> On Wed, 2016-03-23 at 17:38 +0100, Paulina Szubarczyk wrote:
>> Hi,
>>
>> Thank you for the proposed tasks. I would like to work on the second
>> one,
>> fixing the return codes in xl.
>>
> I just wanted to say that, since I've done (and mentored) some similar
> activity before, so, if you go for this, feel free to ask and/or to Cc
> me to the patches as well. :-)
>
> Regards,
> Dario
> --
> <<This happens because I choose it to happen!>> (Raistlin Majere)
> -----------------------------------------------------------------
> Dario Faggioli, Ph.D, http://about.me/dario.faggioli
> Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
>
[-- Attachment #1.2: Type: text/html, Size: 2991 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-01 10:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 15:32 Outreachy bite-sized tasks Roger Pau Monné
2016-03-23 16:38 ` Paulina Szubarczyk
2016-03-23 18:21 ` Dario Faggioli
2016-04-01 10:05 ` Paulina Szubarczyk [this message]
2016-04-01 13:35 ` Roger Pau Monné
2016-04-20 10:06 ` Paulina Szubarczyk
2016-04-25 18:58 ` Konrad Rzeszutek Wilk
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=CAMQpU2rsaSNMCJeyzAWNgL_PW4HrD8LthkcVspH9jSayWwKTTA@mail.gmail.com \
--to=paulinaszubarczyk@gmail.com \
--cc=dario.faggioli@citrix.com \
--cc=mina.naghshnejad@gmail.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/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;
as well as URLs for NNTP newsgroup(s).