* OVS Kernel Datapath development
@ 2014-12-08 4:47 Pravin Shelar
2014-12-08 17:15 ` [ovs-dev] " Thomas Graf
` (2 more replies)
0 siblings, 3 replies; 8+ messages in thread
From: Pravin Shelar @ 2014-12-08 4:47 UTC (permalink / raw)
To: netdev, dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org
Since the beginning OVS kernel datapath development is primarily done
on external OVS repo. Now we have mostly synced upstream and external
OVS. So we have decided to change this process. New process is as
follows.
1. OVS feature development that involves kernel datapath should be
done on net-next tree datapath.
2. Such feature patch series should be posted on netdev and ovs-dev
mailing list.
3. Once review is done for entire series, kernel and OVS userspace
patches will be merged in respective repo.
4. After the merge developer is suppose to send patches for external
kernel datapath along with old kernel compatibility code. So that we
can keep external datapath insync.
Thanks,
Pravin.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [ovs-dev] OVS Kernel Datapath development
2014-12-08 4:47 OVS Kernel Datapath development Pravin Shelar
@ 2014-12-08 17:15 ` Thomas Graf
2014-12-08 18:30 ` Pravin Shelar
2014-12-09 12:52 ` Flavio Leitner
[not found] ` <CALnjE+rn_Giv+8TM1_E2faBftRkivXMYHcjn-4Eq4Gu15r=CiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2 siblings, 1 reply; 8+ messages in thread
From: Thomas Graf @ 2014-12-08 17:15 UTC (permalink / raw)
To: Pravin Shelar; +Cc: netdev, dev@openvswitch.org
On 12/07/14 at 08:47pm, Pravin Shelar wrote:
> Since the beginning OVS kernel datapath development is primarily done
> on external OVS repo. Now we have mostly synced upstream and external
> OVS. So we have decided to change this process. New process is as
> follows.
>
> 1. OVS feature development that involves kernel datapath should be
> done on net-next tree datapath.
> 2. Such feature patch series should be posted on netdev and ovs-dev
> mailing list.
> 3. Once review is done for entire series, kernel and OVS userspace
> patches will be merged in respective repo.
> 4. After the merge developer is suppose to send patches for external
> kernel datapath along with old kernel compatibility code. So that we
> can keep external datapath insync.
+1
Just to be clear, by respective repo do you mean net-next/net or will
you maintain a net-next branch on git.kernel.org and continue doing
pull requests?
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [ovs-dev] OVS Kernel Datapath development
2014-12-08 17:15 ` [ovs-dev] " Thomas Graf
@ 2014-12-08 18:30 ` Pravin Shelar
2014-12-09 14:59 ` Thomas F Herbert
0 siblings, 1 reply; 8+ messages in thread
From: Pravin Shelar @ 2014-12-08 18:30 UTC (permalink / raw)
To: Thomas Graf; +Cc: netdev, dev@openvswitch.org
On Mon, Dec 8, 2014 at 9:15 AM, Thomas Graf <tgraf@noironetworks.com> wrote:
> On 12/07/14 at 08:47pm, Pravin Shelar wrote:
>> Since the beginning OVS kernel datapath development is primarily done
>> on external OVS repo. Now we have mostly synced upstream and external
>> OVS. So we have decided to change this process. New process is as
>> follows.
>>
>> 1. OVS feature development that involves kernel datapath should be
>> done on net-next tree datapath.
>> 2. Such feature patch series should be posted on netdev and ovs-dev
>> mailing list.
>> 3. Once review is done for entire series, kernel and OVS userspace
>> patches will be merged in respective repo.
>> 4. After the merge developer is suppose to send patches for external
>> kernel datapath along with old kernel compatibility code. So that we
>> can keep external datapath insync.
>
> +1
>
> Just to be clear, by respective repo do you mean net-next/net or will
> you maintain a net-next branch on git.kernel.org and continue doing
> pull requests?
OVS patches will directly go to net-next/net tree. I am not planning
on maintaining any tree on git.kernel.org.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [ovs-dev] OVS Kernel Datapath development
2014-12-08 18:30 ` Pravin Shelar
@ 2014-12-09 14:59 ` Thomas F Herbert
2014-12-09 17:34 ` Pravin Shelar
0 siblings, 1 reply; 8+ messages in thread
From: Thomas F Herbert @ 2014-12-09 14:59 UTC (permalink / raw)
To: Pravin Shelar, Thomas Graf; +Cc: dev@openvswitch.org, netdev
Thanks.
What is the impact on a developer submitting a patch. Do we now submit
the linux datapath portion of the patch to both netdev and ovs-dev?
--Tom
On 12/8/14, 1:30 PM, Pravin Shelar wrote:
> On Mon, Dec 8, 2014 at 9:15 AM, Thomas Graf <tgraf@noironetworks.com> wrote:
>> On 12/07/14 at 08:47pm, Pravin Shelar wrote:
>>> Since the beginning OVS kernel datapath development is primarily done
>>> on external OVS repo. Now we have mostly synced upstream and external
>>> OVS. So we have decided to change this process. New process is as
>>> follows.
>>>
>>> 1. OVS feature development that involves kernel datapath should be
>>> done on net-next tree datapath.
>>> 2. Such feature patch series should be posted on netdev and ovs-dev
>>> mailing list.
>>> 3. Once review is done for entire series, kernel and OVS userspace
>>> patches will be merged in respective repo.
>>> 4. After the merge developer is suppose to send patches for external
>>> kernel datapath along with old kernel compatibility code. So that we
>>> can keep external datapath insync.
>> +1
>>
>> Just to be clear, by respective repo do you mean net-next/net or will
>> you maintain a net-next branch on git.kernel.org and continue doing
>> pull requests?
> OVS patches will directly go to net-next/net tree. I am not planning
> on maintaining any tree on git.kernel.org.
> _______________________________________________
> dev mailing list
> dev@openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
--
Thomas F. Herbert
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [ovs-dev] OVS Kernel Datapath development
2014-12-09 14:59 ` Thomas F Herbert
@ 2014-12-09 17:34 ` Pravin Shelar
0 siblings, 0 replies; 8+ messages in thread
From: Pravin Shelar @ 2014-12-09 17:34 UTC (permalink / raw)
To: thomasfherbert; +Cc: Thomas Graf, dev@openvswitch.org, netdev
On Tue, Dec 9, 2014 at 6:59 AM, Thomas F Herbert
<thomasfherbert@gmail.com> wrote:
> Thanks.
>
> What is the impact on a developer submitting a patch. Do we now submit the
> linux datapath portion of the patch to both netdev and ovs-dev?
>
Yes, if a feature needs kernel datapath changes the feature series
should be posted on both mailing lists.
> --Tom
>
>
> On 12/8/14, 1:30 PM, Pravin Shelar wrote:
>>
>> On Mon, Dec 8, 2014 at 9:15 AM, Thomas Graf <tgraf@noironetworks.com>
>> wrote:
>>>
>>> On 12/07/14 at 08:47pm, Pravin Shelar wrote:
>>>>
>>>> Since the beginning OVS kernel datapath development is primarily done
>>>> on external OVS repo. Now we have mostly synced upstream and external
>>>> OVS. So we have decided to change this process. New process is as
>>>> follows.
>>>>
>>>> 1. OVS feature development that involves kernel datapath should be
>>>> done on net-next tree datapath.
>>>> 2. Such feature patch series should be posted on netdev and ovs-dev
>>>> mailing list.
>>>> 3. Once review is done for entire series, kernel and OVS userspace
>>>> patches will be merged in respective repo.
>>>> 4. After the merge developer is suppose to send patches for external
>>>> kernel datapath along with old kernel compatibility code. So that we
>>>> can keep external datapath insync.
>>>
>>> +1
>>>
>>> Just to be clear, by respective repo do you mean net-next/net or will
>>> you maintain a net-next branch on git.kernel.org and continue doing
>>> pull requests?
>>
>> OVS patches will directly go to net-next/net tree. I am not planning
>> on maintaining any tree on git.kernel.org.
>> _______________________________________________
>> dev mailing list
>> dev@openvswitch.org
>> http://openvswitch.org/mailman/listinfo/dev
>
>
>
> --
> Thomas F. Herbert
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: OVS Kernel Datapath development
2014-12-08 4:47 OVS Kernel Datapath development Pravin Shelar
2014-12-08 17:15 ` [ovs-dev] " Thomas Graf
@ 2014-12-09 12:52 ` Flavio Leitner
[not found] ` <CALnjE+rn_Giv+8TM1_E2faBftRkivXMYHcjn-4Eq4Gu15r=CiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2 siblings, 0 replies; 8+ messages in thread
From: Flavio Leitner @ 2014-12-09 12:52 UTC (permalink / raw)
To: Pravin Shelar; +Cc: netdev, dev@openvswitch.org
On Sun, Dec 07, 2014 at 08:47:22PM -0800, Pravin Shelar wrote:
> Since the beginning OVS kernel datapath development is primarily done
> on external OVS repo. Now we have mostly synced upstream and external
> OVS. So we have decided to change this process. New process is as
> follows.
>
> 1. OVS feature development that involves kernel datapath should be
> done on net-next tree datapath.
> 2. Such feature patch series should be posted on netdev and ovs-dev
> mailing list.
> 3. Once review is done for entire series, kernel and OVS userspace
> patches will be merged in respective repo.
> 4. After the merge developer is suppose to send patches for external
> kernel datapath along with old kernel compatibility code. So that we
> can keep external datapath insync.
This is great! Thanks for changing the development process and
make it official.
Cheers!
fbl
^ permalink raw reply [flat|nested] 8+ messages in thread[parent not found: <CALnjE+rn_Giv+8TM1_E2faBftRkivXMYHcjn-4Eq4Gu15r=CiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>]
* Re: OVS Kernel Datapath development
[not found] ` <CALnjE+rn_Giv+8TM1_E2faBftRkivXMYHcjn-4Eq4Gu15r=CiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2014-12-09 18:02 ` Lori Jakab
2014-12-09 18:36 ` [ovs-dev] " Pravin Shelar
0 siblings, 1 reply; 8+ messages in thread
From: Lori Jakab @ 2014-12-09 18:02 UTC (permalink / raw)
To: Pravin Shelar, netdev,
dev-yBygre7rU0TnMu66kgdUjQ@public.gmane.org
On 12/08/2014 06:47 AM, Pravin Shelar wrote:
> Since the beginning OVS kernel datapath development is primarily done
> on external OVS repo. Now we have mostly synced upstream and external
> OVS. So we have decided to change this process. New process is as
> follows.
Patch series that have previous revisions already reviewed with the old
process should now switch to the new process? Or does the change apply
only to new patch series?
-Lori
>
> 1. OVS feature development that involves kernel datapath should be
> done on net-next tree datapath.
> 2. Such feature patch series should be posted on netdev and ovs-dev
> mailing list.
> 3. Once review is done for entire series, kernel and OVS userspace
> patches will be merged in respective repo.
> 4. After the merge developer is suppose to send patches for external
> kernel datapath along with old kernel compatibility code. So that we
> can keep external datapath insync.
>
>
> Thanks,
> Pravin.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
^ permalink raw reply [flat|nested] 8+ messages in thread* Re: [ovs-dev] OVS Kernel Datapath development
2014-12-09 18:02 ` Lori Jakab
@ 2014-12-09 18:36 ` Pravin Shelar
0 siblings, 0 replies; 8+ messages in thread
From: Pravin Shelar @ 2014-12-09 18:36 UTC (permalink / raw)
To: Lori Jakab; +Cc: netdev, dev@openvswitch.org
On Tue, Dec 9, 2014 at 10:02 AM, Lori Jakab <lojakab@cisco.com> wrote:
> On 12/08/2014 06:47 AM, Pravin Shelar wrote:
>> Since the beginning OVS kernel datapath development is primarily done
>> on external OVS repo. Now we have mostly synced upstream and external
>> OVS. So we have decided to change this process. New process is as
>> follows.
>
> Patch series that have previous revisions already reviewed with the old
> process should now switch to the new process? Or does the change apply
> only to new patch series?
>
All patch series should follow new process including the one which got
reviewed partially.
> -Lori
>
>>
>> 1. OVS feature development that involves kernel datapath should be
>> done on net-next tree datapath.
>> 2. Such feature patch series should be posted on netdev and ovs-dev
>> mailing list.
>> 3. Once review is done for entire series, kernel and OVS userspace
>> patches will be merged in respective repo.
>> 4. After the merge developer is suppose to send patches for external
>> kernel datapath along with old kernel compatibility code. So that we
>> can keep external datapath insync.
>>
>>
>> Thanks,
>> Pravin.
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2014-12-09 18:36 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-12-08 4:47 OVS Kernel Datapath development Pravin Shelar
2014-12-08 17:15 ` [ovs-dev] " Thomas Graf
2014-12-08 18:30 ` Pravin Shelar
2014-12-09 14:59 ` Thomas F Herbert
2014-12-09 17:34 ` Pravin Shelar
2014-12-09 12:52 ` Flavio Leitner
[not found] ` <CALnjE+rn_Giv+8TM1_E2faBftRkivXMYHcjn-4Eq4Gu15r=CiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-12-09 18:02 ` Lori Jakab
2014-12-09 18:36 ` [ovs-dev] " Pravin Shelar
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).