* [lustre-devel] Working on client merge
@ 2015-06-09 14:08 Ben Evans
2015-06-10 17:14 ` Simmons, James A.
0 siblings, 1 reply; 6+ messages in thread
From: Ben Evans @ 2015-06-09 14:08 UTC (permalink / raw
To: lustre-devel
Where would be a good place to get started with helping merge the client into mainline?
Thanks
-Ben Evans
bevans at cray.com<mailto:bevans@cray.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20150609/11a65f09/attachment-0001.htm>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lustre-devel] Working on client merge
2015-06-09 14:08 [lustre-devel] Working on client merge Ben Evans
@ 2015-06-10 17:14 ` Simmons, James A.
2015-06-10 17:16 ` Julia Lawall
2015-06-10 18:14 ` Christopher J. Morrone
0 siblings, 2 replies; 6+ messages in thread
From: Simmons, James A. @ 2015-06-10 17:14 UTC (permalink / raw
To: lustre-devel
>Where would be a good place to get started with helping merge the client into mainline?
Hi Ben
Thanks for helping out for this work. I added people in the chain that have contributed a great
deal to the upstream client so we can coordinate our work. Also I like to make people aware
a lustre IRC channel does exist. Andreas can supply the details about the IRC channel. Currently
my work has been focused on the libcfs/lnet layer. I had discuss early with Mike Shuey since he
was also working in that area but will be migrating to the lustre core.
Since more people are getting involved we need to find a way to break up the work to avoid
duplicate work. Should the work be broken up by layer, i.e lov, mdc, or by task such as removing
specific checkpatch errors with files?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20150610/b0e9cf7d/attachment.htm>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lustre-devel] Working on client merge
2015-06-10 17:14 ` Simmons, James A.
@ 2015-06-10 17:16 ` Julia Lawall
2015-06-10 17:59 ` Patrick Farrell
2015-06-10 18:14 ` Christopher J. Morrone
1 sibling, 1 reply; 6+ messages in thread
From: Julia Lawall @ 2015-06-10 17:16 UTC (permalink / raw
To: lustre-devel
On Wed, 10 Jun 2015, Simmons, James A. wrote:
>
> >Where would be a good place to get started with helping merge the client
> into mainline?
>
> ?
>
> Hi Ben
>
> ?
>
> ???? Thanks for helping out for this work. I added people in the chain that
> have contributed a great
>
> deal to the upstream client so we can coordinate our work. Also I like to
> make people aware
>
> a lustre IRC channel does exist. ??Andreas can supply the details about the
> IRC channel. Currently
>
> my work has been focused on the libcfs/lnet layer. I had discuss early with
> Mike Shuey ?since he
>
> was also working in that area but will be migrating to the lustre core.
>
> ?
>
> ??? Since more people are getting involved we need to find? a way to break
> up the work to avoid
>
> duplicate work. Should the work be broken ?up by layer, i.e lov, mdc, or by
> task such as removing
>
> specific checkpatch errors with files?
For the work I have done with Coccinelle, it is more convenient to do the
whole thing. Breaking things up by layer is not helpful.
This is just a data point, though. It doesn't have to imply anything about
how others work on the code.
julia
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lustre-devel] Working on client merge
2015-06-10 17:16 ` Julia Lawall
@ 2015-06-10 17:59 ` Patrick Farrell
2015-06-10 18:11 ` Chris Hanna
0 siblings, 1 reply; 6+ messages in thread
From: Patrick Farrell @ 2015-06-10 17:59 UTC (permalink / raw
To: lustre-devel
I suggest breaking it up first by work type. As Julia noted,
coccinelle/checkpatch/etc fixes (coding style, straightforward errors
caught by the tools, sparse complaints, warnings, etc.) rarely require
awareness of the larger flow of the design.
Then there is some other types of cleanup that require more Lustre
knowledge to tackle. If possible, those would be better for someone
like Ben (or you, James) to work on. What do we have for that kind of work?
- Patrick
On 06/10/2015 12:16 PM, Julia Lawall wrote:
>
> On Wed, 10 Jun 2015, Simmons, James A. wrote:
>
>>> Where would be a good place to get started with helping merge the client
>> into mainline?
>>
>>
>>
>> Hi Ben
>>
>>
>>
>> Thanks for helping out for this work. I added people in the chain that
>> have contributed a great
>>
>> deal to the upstream client so we can coordinate our work. Also I like to
>> make people aware
>>
>> a lustre IRC channel does exist. Andreas can supply the details about the
>> IRC channel. Currently
>>
>> my work has been focused on the libcfs/lnet layer. I had discuss early with
>> Mike Shuey since he
>>
>> was also working in that area but will be migrating to the lustre core.
>>
>>
>>
>> Since more people are getting involved we need to find a way to break
>> up the work to avoid
>>
>> duplicate work. Should the work be broken up by layer, i.e lov, mdc, or by
>> task such as removing
>>
>> specific checkpatch errors with files?
> For the work I have done with Coccinelle, it is more convenient to do the
> whole thing. Breaking things up by layer is not helpful.
>
> This is just a data point, though. It doesn't have to imply anything about
> how others work on the code.
>
> julia
>
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20150610/0dded25b/attachment.htm>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lustre-devel] Working on client merge
2015-06-10 17:59 ` Patrick Farrell
@ 2015-06-10 18:11 ` Chris Hanna
0 siblings, 0 replies; 6+ messages in thread
From: Chris Hanna @ 2015-06-10 18:11 UTC (permalink / raw
To: lustre-devel
I'd be happy to continue work on the format, whitespace, and coding
style changes, on any areas that aren't already spoken for.
Chris
On 6/10/15 1:59 PM, Patrick Farrell wrote:
> I suggest breaking it up first by work type. As Julia noted,
> coccinelle/checkpatch/etc fixes (coding style, straightforward errors
> caught by the tools, sparse complaints, warnings, etc.) rarely require
> awareness of the larger flow of the design.
>
> Then there is some other types of cleanup that require more Lustre
> knowledge to tackle. If possible, those would be better for someone
> like Ben (or you, James) to work on. What do we have for that kind of
> work?
>
> - Patrick
>
> On 06/10/2015 12:16 PM, Julia Lawall wrote:
>>
>> On Wed, 10 Jun 2015, Simmons, James A. wrote:
>>
>>>> Where would be a good place to get started with helping merge the
>>>> client
>>> into mainline?
>>>
>>>
>>> Hi Ben
>>>
>>>
>>> Thanks for helping out for this work. I added people in the
>>> chain that
>>> have contributed a great
>>>
>>> deal to the upstream client so we can coordinate our work. Also I
>>> like to
>>> make people aware
>>>
>>> a lustre IRC channel does exist. Andreas can supply the details
>>> about the
>>> IRC channel. Currently
>>>
>>> my work has been focused on the libcfs/lnet layer. I had discuss
>>> early with
>>> Mike Shuey since he
>>>
>>> was also working in that area but will be migrating to the lustre core.
>>>
>>>
>>> Since more people are getting involved we need to find a way
>>> to break
>>> up the work to avoid
>>>
>>> duplicate work. Should the work be broken up by layer, i.e lov,
>>> mdc, or by
>>> task such as removing
>>>
>>> specific checkpatch errors with files?
>> For the work I have done with Coccinelle, it is more convenient to do
>> the
>> whole thing. Breaking things up by layer is not helpful.
>>
>> This is just a data point, though. It doesn't have to imply anything
>> about
>> how others work on the code.
>>
>> julia
>>
>>
>> _______________________________________________
>> lustre-devel mailing list
>> lustre-devel at lists.lustre.org
>> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>
>
>
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20150610/3241ab71/attachment-0001.htm>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [lustre-devel] Working on client merge
2015-06-10 17:14 ` Simmons, James A.
2015-06-10 17:16 ` Julia Lawall
@ 2015-06-10 18:14 ` Christopher J. Morrone
1 sibling, 0 replies; 6+ messages in thread
From: Christopher J. Morrone @ 2015-06-10 18:14 UTC (permalink / raw
To: lustre-devel
Justin Miller also made the IRC details also available here:
http://wiki.lustre.org/Mailing_Lists_and_IRC
Chris
On 06/10/2015 10:14 AM, Simmons, James A. wrote:
>>Where would be a good place to get started with helping merge the client
> into mainline?
>
> Hi Ben
>
> Thanks for helping out for this work. I added people in the chain
> that have contributed a great
>
> deal to the upstream client so we can coordinate our work. Also I like
> to make people aware
>
> a lustre IRC channel does exist. Andreas can supply the details about
> the IRC channel. Currently
>
> my work has been focused on the libcfs/lnet layer. I had discuss early
> with Mike Shuey since he
>
> was also working in that area but will be migrating to the lustre core.
>
> Since more people are getting involved we need to find a way to
> break up the work to avoid
>
> duplicate work. Should the work be broken up by layer, i.e lov, mdc, or
> by task such as removing
>
> specific checkpatch errors with files?
>
>
>
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-06-10 18:14 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-09 14:08 [lustre-devel] Working on client merge Ben Evans
2015-06-10 17:14 ` Simmons, James A.
2015-06-10 17:16 ` Julia Lawall
2015-06-10 17:59 ` Patrick Farrell
2015-06-10 18:11 ` Chris Hanna
2015-06-10 18:14 ` Christopher J. Morrone
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.