Hi, What ''priority'' has the whole tcp/ip traffic which is not marked with ''flowadm''? Is it marked as ''medium''? -- Regards, Piotr Jasiukajtis | estibi | SCA OS0072 http://estseg.blogspot.com
On 12/01/08 09:21, Piotr Jasiukajtis wrote:> Hi, > > What ''priority'' has the whole tcp/ip traffic which is not marked with ''flowadm''? > Is it marked as ''medium''? >If you don''t have any flows configured on an interface then the priority for that link would be by default *high* (and hence the packets received/transmitted by the interface). bash-3.2# dladm show-linkprop e1000g0 | egrep "(priority|LINK)" LINK PROPERTY VALUE DEFAULT POSSIBLE e1000g0 priority -- High Low,Medium,High thanks ~Girish
Ok, thanks. Girish Moodalbail pisze:> On 12/01/08 09:21, Piotr Jasiukajtis wrote: >> Hi, >> >> What ''priority'' has the whole tcp/ip traffic which is not marked with >> ''flowadm''? >> Is it marked as ''medium''? >> > If you don''t have any flows configured on an interface then the priority > for that link would be by default *high* (and hence the packets > received/transmitted by the interface). > > bash-3.2# dladm show-linkprop e1000g0 | egrep "(priority|LINK)" > LINK PROPERTY VALUE DEFAULT POSSIBLE > e1000g0 priority -- High Low,Medium,High > > thanks > ~Girish > >-- Regards, Piotr Jasiukajtis | estibi | SCA OS0072 http://estseg.blogspot.com
> > What ''priority'' has the whole tcp/ip traffic which is not marked with ''flowadm''?> > Is it marked as ''medium''? > > > If you don''t have any flows configured on an interface then the priority > for that link would be by default *high* (and hence the packets > received/transmitted by the interface). > > bash-3.2# dladm show-linkprop e1000g0 | egrep "(priority|LINK)" > LINK PROPERTY VALUE DEFAULT POSSIBLE > e1000g0 priority -- High Low,Medium,High If the default is "high", why isn''t the value shown as "high"? If the intent is to show that the default is being used, then we should invent a syntax to do that, rather than overload "--" (which for some properties is itself a valid value that may have been explicitly chosen by the admin). (Also, what''s with the capitalization? I don''t recall this for any existing link properties.) -- meem
On 12/01/08 16:50, Peter Memishian wrote:> > > What ''priority'' has the whole tcp/ip traffic which is not marked with ''flowadm''? > > > Is it marked as ''medium''? > > > > > If you don''t have any flows configured on an interface then the priority > > for that link would be by default *high* (and hence the packets > > received/transmitted by the interface). > > > > bash-3.2# dladm show-linkprop e1000g0 | egrep "(priority|LINK)" > > LINK PROPERTY VALUE DEFAULT POSSIBLE > > e1000g0 priority -- High Low,Medium,High > > If the default is "high", why isn''t the value shown as "high"? If the > intent is to show that the default is being used, then we should invent a > syntax to do that, rather than overload "--" (which for some properties is > itself a valid value that may have been explicitly chosen by the admin). > (Also, what''s with the capitalization? I don''t recall this for any > existing link properties.) >Correct, the possible values shouldn''t be capitalized to be consistent with other link properties. Further the default value needs to be reiterated under the *VALUE* column like all other link properties. I will open a P4 CR to track this. thanks ~Girish
> > > If you don''t have any flows configured on an interface then the priority> > > for that link would be by default *high* (and hence the packets > > > received/transmitted by the interface). > > > > > > bash-3.2# dladm show-linkprop e1000g0 | egrep "(priority|LINK)" > > > LINK PROPERTY VALUE DEFAULT POSSIBLE > > > e1000g0 priority -- High Low,Medium,High > > > > If the default is "high", why isn''t the value shown as "high"? If the > > intent is to show that the default is being used, then we should invent a > > syntax to do that, rather than overload "--" (which for some properties is > > itself a valid value that may have been explicitly chosen by the admin). > > (Also, what''s with the capitalization? I don''t recall this for any > > existing link properties.) > > > Correct, the possible values shouldn''t be capitalized to be consistent > with other link properties. Further the default value needs to be > reiterated under the *VALUE* column like all other link properties. I > will open a P4 CR to track this. Great, thanks. To be clear: I think there is value in having a way to indicate that the default is being used. (If nothing else, internally it''s important when upgrading to bits that have changed the default.) I''ve cc''d brussels-dev here in case they''re already tracking such an RFE. -- meem