From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Gerard Spivey <gerard.spivey@gmail.com>
Cc: xen-devel@lists.xen.org
Subject: Re: CPU/RAM/PCI diagram tool
Date: Thu, 27 Feb 2014 14:48:50 +0000 [thread overview]
Message-ID: <530F5052.8040308@citrix.com> (raw)
In-Reply-To: <9FF1CEF2-0669-405A-9CAF-3059315B7D63@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1151 bytes --]
On 27/02/14 04:48, Gerard Spivey wrote:
> Hello All,
>
> My name is Gerard.
> I am new to the Xen development community and would like to get started.
> I saw the Xen development projects list and will start on the
> CPU/RAM/PCI diagram tool as my first project.
>
> During my day job I’m a software developer writing networking
> applications for a variety of computing architectures (x86, Tilera,
> and more),
> using technologies similar to and including PF_RINGS and DPDK. Due to
> the work I’ve been doing the past few years Ive taken an interest in
> the Xen project.
>
> I’m looking forward to to working on the project and engaging with the
> Xen developer community.
> I’m on the ##xen channel as SpiffySpivey.
>
> Thanks!
>
>
> Gerard
Hello,
Thankyou for taking an interest.
Having a day job, I presume you are not associated with GSoC, and are
doing this of your own volition? As you can imagine, there is
substantially more than 1 projects worth of potential work to be done,
and plenty of room for expansion.
How much knowledge do you have x86 architecture and system topology, or
the methods of conveying this information?
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 4229 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:[~2014-02-27 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 4:48 CPU/RAM/PCI diagram tool Gerard Spivey
2014-02-27 14:48 ` Andrew Cooper [this message]
2014-03-05 5:01 ` Gerard Spivey
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=530F5052.8040308@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=gerard.spivey@gmail.com \
--cc=xen-devel@lists.xen.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).