From: Gerard Spivey <gerard.spivey@gmail.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel@lists.xen.org
Subject: Re: CPU/RAM/PCI diagram tool
Date: Wed, 5 Mar 2014 00:01:43 -0500 [thread overview]
Message-ID: <CADopG42wLg0yHJ6AWHi9PyMgRM4fYACTKbxJoKakmJZsAt9RjQ@mail.gmail.com> (raw)
In-Reply-To: <530F5052.8040308@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1645 bytes --]
Andrew,
I apologize for the delayed response.
I'm not associated with GSoC, doing this purely out of my own interest.
I have a pretty solid knowledge of x86 system topology.
Aware of concepts like CPU/SOC having integrated north bridge. NUMA zones
of a server platform separated via QPI/HT links, etc.
I don't have much experience displaying this information.
Gerard
On Thu, Feb 27, 2014 at 9:48 AM, Andrew Cooper <andrew.cooper3@citrix.com>wrote:
> 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: 4794 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-03-05 5:01 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
2014-03-05 5:01 ` Gerard Spivey [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=CADopG42wLg0yHJ6AWHi9PyMgRM4fYACTKbxJoKakmJZsAt9RjQ@mail.gmail.com \
--to=gerard.spivey@gmail.com \
--cc=andrew.cooper3@citrix.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).