AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<David.Olien@lsi.com>,<Craig.Thomas@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	6C678488C5CEE74F813A4D1948FD2DC7B7B2532B@cosmail02.lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 16 Mar 2010 11:22:33 -0700
From: Andrew Sharp <andy.sharp@lsi.com>
To: "Olien, David" <David.Olien@lsi.com>
Cc: "Thomas, Craig" <Craig.Thomas@lsi.com>
Subject: Re: Tuxtor work
Message-ID: <20100316112233.0bfcfdb3@ripper.onstor.net>
In-Reply-To: <6C678488C5CEE74F813A4D1948FD2DC7B7B2532B@cosmail02.lsi.com>
References: <6C678488C5CEE74F813A4D1948FD2DC7B7B2532B@cosmail02.lsi.com>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Mon, 15 Mar 2010 18:25:19 -0600 "Olien, David" <David.Olien@lsi.com>
wrote:

> Hi Andy,
> 
> I've been told that I'll be helping out with some  tuxtor
> development.   I'll be glad to do whatever I can.

How'd you draw the short straw?  I thought Sam was [slightly] keen on
doing some of this cruft?

> I've seen your tuxtor schedule chart.  I see 5 items listed for
> people here in Beaverton.  Initially at least, I'll try to take all
> of these tasks.  I also understand you have some sort of May 18
> deadline for all of the work on this schedule to be completed.
> 
> I'm going to list the work items, along with what I think these
> mean.  Can you fill in whatever details you can,  I'll then try to
> give an estimate, with the May 18 deadline in mind.  I'm looking at
> the  wiki page for the tuxstor threads port.  My linux desktop is
> hung right now, and I'm waiting for someone to reboot it.  So these
> my are guesses without looking at what's already written.
> 
> Here's the work items and what I THINK they mean.

I think maybe the best thing to do is set up a conference call with Max
because he's the person who actually understands these tasks at the
lowest level.  I'll set that up and let you know.


> 1.       Update FP and TXRX memory handling algorithms (chart
> estimate 16 hr (2 days)) I'm guessing that most of this code is
> already there, or can be adapted from the existing cougar source
> code.  The basic requirement is the non-blocking, non-failing
> semantics. These are the interfaces implemented in eee-mem.h,
> eee-mem.c?

Nah, ask Sam what he did recently for EEE.  It will be similar.  I
hope.  I think we just have some stuff that assumes 32 bits will be
enough to hold an address.


> 2.       ESM thread core dump support (chart estimate 40h (1 week))
> 
> This is support for dumping out the contents of memory for the fp and
> txrx "cores" (i.e. the Linux kernel threads that provide the
> execution context for the eee threads) , along with information about
> eee threads that are running on those "cores", ESM being the
> lower-level implementation  that supports the
> thread_create()/thread_exit()/thread_yield().   Also include the
> "per-core" private memory.
> 
> 
> 
> 3.       Core dump support (chart estimate 40h (1 week))
> 
> I'm not sure where number 2 ends and number 3 begins

One is all the memory in the entire world (kernel core dump, which,
BTW, might be there already, but would need some testing and possibly
tweaking), and the other is just a core dump of an ESM thread itself.


> 4.       Implement FS writestacks support (chart estimate 24 hr (3
> days))
> 
> Looks like this has to do with displaying validthread stacks via the
> fscmd writestacks command.
> 
> 
> 
> 5.       Kgdb support for ESM threads (chart estimate 80 hr (two
> weeks))
> 
> I'm guessing this refers to the .gdbinit file used when debugging?
> 
> Am I at least on the right track?

Anything's possible.

I'll set up a chat with Max, that should be quite educational.

Cheers,

a
