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:<bill.fisher@lsi.com>,<Brian.Stark@lsi.com>,<Bill.Fisher@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/LSI/INBOX	0	4AF08466.6020003@lsi.com
X-Sylpheed-End-Special-Headers: 1
Date: Tue, 3 Nov 2009 13:33:20 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: William Fisher <bill.fisher@lsi.com>
Cc: "Stark, Brian" <Brian.Stark@lsi.com>, "Fisher, Bill"
 <Bill.Fisher@lsi.com>
Subject: Re: Staffing the Linux FP Software Porting Effort
Message-ID: <20091103133320.4049b5f1@ripper.onstor.net>
In-Reply-To: <4AF08466.6020003@lsi.com>
References: <4AF08466.6020003@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 Tue, 3 Nov 2009 12:28:38 -0700 William Fisher <bill.fisher@lsi.com>
wrote:

> Brian:
> 
> I was thinking about Max's reluctance to work on the
> Linux FP porting effort last night, so I was going to suggest
> an alternative/modification of sorts;
> 
> 1) We convince Max to implement the FP thread package
>     with the resource release feature for locks, memory, etc.
>     ONLY. Nothing else except some consulting on the code.

A minor win but a win if we can get it.

> 2) We convince Ed to allow swapping Danqing Jin who's
>     working on escalations for Max and have Danqing Jin
>     do the port of the FP code. Max would agree to
>     do some FP consulting if needed.

I'm fine with that but I have no way to gauge DJ's viability w.r.t. the
effort.

> 3) The win-win here is: Danqing Jin gets to learn more
>     of the FP code over an above the FS portions he already
>     knows. Max gets to continue working on EEE, some
>     escalations and the GNS software development tasks.

Assuming we can Max to do anything, but yeah.

> 4) We recruit another Linux engineer to work
>     with us on the software integration/porting
>     to x86 and the Xen work. This would include
>     the toolchain, drivers, Xen configurations, etc.

That's the same; we're continuing to try and recruit another engineer
for the project.


> Comments?
> 
> -- Bill
