[P4-dev] I have some problems about the p4runtime.proto.

Antonin Bas antonin at barefootnetworks.com
Fri Jul 7 15:09:01 EDT 2017


Hi,

I think I answered all your questions in the Github issue you opened:
https://github.com/p4lang/behavioral-model/issues/407. If not, please use
the Github issue to follow-up so everything is in one place.

Thanks,

Antonin

On Thu, Jul 6, 2017 at 1:21 AM, <ding.rui at zte.com.cn> wrote:

> Hi, everyone,
>
> I have some problems about the p4runtime.proto.
>
>
> message SetForwardingPipelineConfigRequest {
>
>   enum Action {
>
>     UNSPECIFIED = 0;
>
>     VERIFY = 1;
>
>     VERIFY_AND_SAVE = 2;
>
>     VERIFY_AND_COMMIT = 3;
>
>     COMMIT = 4;
>
>   }
>
>   Action action = 1;
>
>   repeated ForwardingPipelineConfig configs = 2;
>
> }
>
>
> message SetForwardingPipelineConfigResponse {
>
> }
>
> message ForwardingPipelineConfig {
>
>   uint64 device_id = 1;     //what's the meaning of the device_id?  I
> think it means the number of P4 chips,
>
>                                           a board may contains many P4
> chips, but for bmv2 it must be 0, is it right?
>
>   config.P4Info p4info = 2;
>
>   // Target-specific P4 configuration.
>
>   bytes p4_device_config = 3;  //  In the demo(https://github.com/
> p4lang/behavioral-model/blob/master/targets/simple_switch_
> grpc/tests/test.cpp),
>
>                                                     it doesn't set the "
> p4_device_config" field, where does the bmv2 run logical come from?  I
> think "p4_device_config"
>
>                                                     and "p4info " must be
> set when initialize bmv2.  What will happen when "p4info" and "p4_device_config"
> come from
>
>                                                     different P4 source
> code?
>
> }
>
> message GetForwardingPipelineConfigRequest {
>
>   repeated uint32 device_ids = 1;
>
> }
>
> message GetForwardingPipelineConfigResponse {
>
>   repeated ForwardingPipelineConfig configs = 1;
>
> }
>
>
>
>
>
>
> 丁瑞 dingrui
>
>
> IT开发工程师 IT Development Engineer
> 南京协议开发一部/有线研究院/有线产品经营部 Nanjing Protocol Development Dept. I/Wireline
> Product Operation Division
>
>
>
> 南京市雨花台区紫荆花路68号中兴通讯
> R&D Building, Zi Jinghua Road 68#,
>
> Yu Huatai District, Nanjing, P..R.China, 210012
>
> M: +86 13584003271 <+86%20135%208400%203271>
> E: ding.rui at zte.com.cn
> www.zte.com.cn
>
> _______________________________________________
> P4-dev mailing list
> P4-dev at lists.p4.org
> http://lists.p4.org/mailman/listinfo/p4-dev_lists.p4.org
>



-- 
Antonin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.p4.org/pipermail/p4-dev_lists.p4.org/attachments/20170707/a50bdaf4/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 9ae3e214c17d49ed935d87c674ba3ee2.jpg
Type: image/jpeg
Size: 6015 bytes
Desc: not available
URL: <http://lists.p4.org/pipermail/p4-dev_lists.p4.org/attachments/20170707/a50bdaf4/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 24242e5637af428891c4db731e7765ad.jpg
Type: image/jpeg
Size: 2064 bytes
Desc: not available
URL: <http://lists.p4.org/pipermail/p4-dev_lists.p4.org/attachments/20170707/a50bdaf4/attachment-0001.jpg>


More information about the P4-dev mailing list