X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B1E3.953E9F9E@onstor-exch02.onstor.net>; Mon, 18 Jun 2007 12:02:22 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7B1E3.953E9F9E"
References: <BB375AF679D4A34E9CA8DFA650E2B04E042A5370@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E032587E0@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E042A572C@onstor-exch02.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: Next steps for eee protocol and mgmt-bus driver.
Date: Mon, 18 Jun 2007 12:01:16 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E032587E2@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Next steps for eee protocol and mgmt-bus driver.
Thread-Index: AcevkdcRlPL+nbdVTsaaFkfNz5sYdwAFS8KUAIehPJAAB3i6Gw==
From: "Richard Beck" <IMCEAEX-_O=ONSTOR_OU=FIRST+20ADMINISTRATIVE+20GROUP_CN=RECIPIENTS_CN=RICHARD+2EBECK@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Tim Gardner" <tim.gardner@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7B1E3.953E9F9E
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm sure I can.  I am just about to give you the initial checkin (item =
1). The other two shouldn't be a problem to finish today.
--Rich


-----Original Message-----
From: Maxim Kozlovsky
Sent: Mon 6/18/2007 9:28 AM
To: Richard Beck; Tim Gardner; Andy Sharp
Subject: RE: Next steps for eee protocol and mgmt-bus driver.
=20
Hello Richard,

=20

I would prefer if you did 1-3 by Monday and 4-6 by Tuesday instead of =
1-6 by Tuesday. Can you do that?

=20

Max

=20

________________________________

From: Richard Beck=20
Sent: Friday, June 15, 2007 4:51 PM
To: Maxim Kozlovsky; Tim Gardner; Andy Sharp
Subject: RE: Next steps for eee protocol and mgmt-bus driver.

=20

Max,

=20

This plan looks good.  The first part should go pretty quickly (1-6).  =
I'm hoping to complete that part by Tuesday.  That will leave the rest =
of the week for the lower level stuff supporting the managment bus =
driver.  Have a good weekend.  See you Monday morning.

=20

--Rich=20

=20

________________________________

From: Maxim Kozlovsky
Sent: Fri 6/15/2007 2:12 PM
To: Richard Beck; Tim Gardner; Andy Sharp
Subject: Next steps for eee protocol and mgmt-bus driver.

Hello Richard,

Here is how I want us to proceed for the rest of your stay with us. I =
don't expect that you (or any other person) will be able to have =
complete debugged implementation of EEE protocol and the management bus =
driver in a week. I would like to get checked in as much as possible of =
code that we all agree works and passes some tests. On the other hand, I =
don't really need the code that is not known to work since it will =
probably be easier for us to start over than to do the debugging for =
you. To accomplish that, I'd like to do the checkins and reviews in =
steps. I will be always available to do the review in the regular =
working hours and will do the review as fast as possible so you are not =
slowed down by multiple reviews. I hope Andy will help as well.

Here is the list of the steps together with the exit criteria:

1)      Check in the kernel configuration changes with empty .c and .h =
files. After these changes, the kernel make in the kernel directory =
should compile the neteee and mgmt bus driver .c files. The =
corresponding .h files should be installed in the appropriate place in =
/usr/include/neteee as part of the build process.

2)      Check in the changes that add AF_EEE/PF_EEE protocol family. =
After these changes, we should be able to create sockets with =
socket(PF_EEE, SOCK_DGRAM, 0).

3)      Check in the changes that add the sockaddr_eee. After these =
changes the following tests should pass:

a)      Bind a socket to a specified address

b)      Negative test for binding a socket with the same address as =
another socket

c)      Negative test for binding a socket to invalid address

d)      Bind a socket to ADDR_ANY - should pickup the next available =
address in reserved range

e)      Test to make sure the address is available again after bound =
socket is closed

4)      Check in the changes to support connect call for AF_EEE sockets. =
Should pass positive tests and negative tests for invalid address.

5)      Check in the code to support send and receive on the loopback =
interfaces. Should pass simple client/server tests for SSC applications =
only.

6)      Check in the code that registers the mgmtbus driver as the =
network driver. Put just minimal amount of the code to make it =
recognizable to the linux kernel, the input/output routines should do =
nothing and just drop the packets. After that we expect to do ifconfig =
on this device and assign ip and eee addresses to it.

7)      Check in the code for sending and receiving the packets through =
the mgmt bus driver. The simple client/server tests between the =
applications on txrx, fp, fc and ssc should pass.

8)      Check in the code to support fragmentation. The tests for =
sending large packets between ssc and embedded cards should pass.

9)      Check in the code for IP forwarding. We will not be able to test =
this part without a lot of other system running.

Max



------_=_NextPart_001_01C7B1E3.953E9F9E
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Next steps for eee protocol and mgmt-bus driver.</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>I'm sure I can.&nbsp; I am just about to give you the =
initial checkin (item 1). The other two shouldn't be a problem to finish =
today.<BR>
--Rich<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: Maxim Kozlovsky<BR>
Sent: Mon 6/18/2007 9:28 AM<BR>
To: Richard Beck; Tim Gardner; Andy Sharp<BR>
Subject: RE: Next steps for eee protocol and mgmt-bus driver.<BR>
<BR>
Hello Richard,<BR>
<BR>
<BR>
<BR>
I would prefer if you did 1-3 by Monday and 4-6 by Tuesday instead of =
1-6 by Tuesday. Can you do that?<BR>
<BR>
<BR>
<BR>
Max<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Richard Beck<BR>
Sent: Friday, June 15, 2007 4:51 PM<BR>
To: Maxim Kozlovsky; Tim Gardner; Andy Sharp<BR>
Subject: RE: Next steps for eee protocol and mgmt-bus driver.<BR>
<BR>
<BR>
<BR>
Max,<BR>
<BR>
<BR>
<BR>
This plan looks good.&nbsp; The first part should go pretty quickly =
(1-6).&nbsp; I'm hoping to complete that part by Tuesday.&nbsp; That =
will leave the rest of the week for the lower level stuff supporting the =
managment bus driver.&nbsp; Have a good weekend.&nbsp; See you Monday =
morning.<BR>
<BR>
<BR>
<BR>
--Rich<BR>
<BR>
<BR>
<BR>
________________________________<BR>
<BR>
From: Maxim Kozlovsky<BR>
Sent: Fri 6/15/2007 2:12 PM<BR>
To: Richard Beck; Tim Gardner; Andy Sharp<BR>
Subject: Next steps for eee protocol and mgmt-bus driver.<BR>
<BR>
Hello Richard,<BR>
<BR>
Here is how I want us to proceed for the rest of your stay with us. I =
don't expect that you (or any other person) will be able to have =
complete debugged implementation of EEE protocol and the management bus =
driver in a week. I would like to get checked in as much as possible of =
code that we all agree works and passes some tests. On the other hand, I =
don't really need the code that is not known to work since it will =
probably be easier for us to start over than to do the debugging for =
you. To accomplish that, I'd like to do the checkins and reviews in =
steps. I will be always available to do the review in the regular =
working hours and will do the review as fast as possible so you are not =
slowed down by multiple reviews. I hope Andy will help as well.<BR>
<BR>
Here is the list of the steps together with the exit criteria:<BR>
<BR>
1)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in the kernel configuration =
changes with empty .c and .h files. After these changes, the kernel make =
in the kernel directory should compile the neteee and mgmt bus driver .c =
files. The corresponding .h files should be installed in the appropriate =
place in /usr/include/neteee as part of the build process.<BR>
<BR>
2)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in the changes that add =
AF_EEE/PF_EEE protocol family. After these changes, we should be able to =
create sockets with socket(PF_EEE, SOCK_DGRAM, 0).<BR>
<BR>
3)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in the changes that add the =
sockaddr_eee. After these changes the following tests should pass:<BR>
<BR>
a)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bind a socket to a specified =
address<BR>
<BR>
b)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Negative test for binding a socket with =
the same address as another socket<BR>
<BR>
c)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Negative test for binding a socket to =
invalid address<BR>
<BR>
d)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Bind a socket to ADDR_ANY - should =
pickup the next available address in reserved range<BR>
<BR>
e)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Test to make sure the address is =
available again after bound socket is closed<BR>
<BR>
4)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in the changes to support connect =
call for AF_EEE sockets. Should pass positive tests and negative tests =
for invalid address.<BR>
<BR>
5)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in the code to support send and =
receive on the loopback interfaces. Should pass simple client/server =
tests for SSC applications only.<BR>
<BR>
6)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in the code that registers the =
mgmtbus driver as the network driver. Put just minimal amount of the =
code to make it recognizable to the linux kernel, the input/output =
routines should do nothing and just drop the packets. After that we =
expect to do ifconfig on this device and assign ip and eee addresses to =
it.<BR>
<BR>
7)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in the code for sending and =
receiving the packets through the mgmt bus driver. The simple =
client/server tests between the applications on txrx, fp, fc and ssc =
should pass.<BR>
<BR>
8)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in the code to support =
fragmentation. The tests for sending large packets between ssc and =
embedded cards should pass.<BR>
<BR>
9)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Check in the code for IP forwarding. We =
will not be able to test this part without a lot of other system =
running.<BR>
<BR>
Max<BR>
<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C7B1E3.953E9F9E--
