search for: linkprop

I decided to take a stab at 6601421 dladm set-linkprop should support multiple -p options along with some related linkprop fixes, but when I looked into dladm.c, was surprised to find that "dladm_parse_props()" is called from do_create_aggr and do_create_vlan in addition to the expected (by me, at least) do_create_vnic *linkprop functions....

...Recv Send Send Socket Socket Message Elapsed Size Size Size Time Throughput bytes bytes bytes secs. 10^6bits/sec 49152 49152 49152 10.00 4018.07 # # dladm set-linkprop -p maxbw=55M znic0 # dladm show-linkprop -p maxbw znic0 LINK PROPERTY PERM VALUE DEFAULT POSSIBLE znic0 maxbw rw 55 -- -- # netperf -H 172.16.17.100 TCP STREAM TEST from ::ffff:0.0.0.0...

Hi, Pradeep: I believe you had some questions about modifying bandwidth for flows/VNICs. I believe that should be fine in the recently released bits, could you please check and lets know if you still have any questions about this. Bandwidth limits can be modified using: links: dladm set-linkprop -p maxbw=<value> linkname flows: flowadm set-flowprop -p maxbw=<value> flowname (I tried netperf after modifying a flow''s bandwidth and it worked fine. If you want us to try some example let us know.) I remember you had questions about monitoring the usage, is that the one?...

...say high, mac_client_open() will initialize the values for the VNIC''s MAC client with the default priority. Subsequently, mac_resource_ctl_set() will result in modifying the priority values for the MAC client to the value corresponding to high. Modifying Priority ------------------ A set-linkprop after the MAC client has been opened can be used to modify the priority of a link. The result is a new priority value and range for the MAC client based on the new priority. Additionally, any flows on top of the MAC client will also need to be reprioritized as the range for the MAC client will cha...

...mark is T5440 and i have tried setting ip_soft_rings_count = 16 on T5440 but result is same . > You might want to run lockstat(1M) to see if the driver routines are implicated as a problem. If the driver is not a problem, then you might want to try CPU binding with dladm set-linkprop -p cpus=0,1,...,24 <link> There may be other things to try here. Also, which OpenSolaris build are you running? In general, running the latest build is recommended for performance work. Regards, -Krishna p.s. crossbow-discuss and/or network-discuss is more appropriate for these que...

...ackets may pass through only if there is a match for their source IP address or sender protocol address (for ARP) on this list. whitelist Packets may pass through only if its type is on the whitelist (discussed below). The dladm command to enable all three types of protection is: dladm set-linkprop -p protection=macnospoof,ipnospoof,whitelist <link> To disable the protection: dladm reset-linkprop -p protection <link> ACLs (access control lists) are used in conjunction with the ipnospoof and whitelist protection types. To manage ACLs, the following subcommands will be added to d...

Folks, I just posted an updated Crossbow virtualization architecture document. The new revision is available at: http://opensolaris.org/os/project/crossbow/Docs/crossbow-virt.pdf The main changes are the addition of support for multiple MAC addresses per client, and an explicit separation between consolidation private and project private MAC API entry points. See in particular the

(Bcc''ed to networking discuss). Hi All, Have enclosed man page draft for dlstat(1M) herewith. This is part of the effort to gain better visibility into network traffic in light of crossbow features like virtual NICs, interrupt vs. polling modes etc. This in turn would greatly assist network performance analysis. It is also aimed at segregating link/flow configuration from

...ative names as message handle cc6090e985d7 net: rtnetlink: introduce helper to get net_device instance by ifname 7af12cba4ef0 net: rtnetlink: unify the code in __rtnl_newlink get dev with the rest 88f4fb0c7496 net: rtnetlink: put alternative names to getlink message 36fbf1e52bd3 net: rtnetlink: add linkprop commands to add and delete alternative ifnames ff92741270bf net: introduce name_node struct to be used in hashlist 6958c97a488c net: procfs: use index hashlist instead of name hashlist be2

I see in NexentaStor''s announcement of Community Edition 3.0.3 they mention some backported patches in this release. Aside from their management features / UI what is the core OS difference if we move to Nexenta from OpenSolaris b134? These DeDup bugs are my main frustration - if a staff member does a rm * in a directory with dedup you can take down the whole storage server - all with

Recently I found that the mac_srs_rx_poll_ring thread may never stop in kernel, please see the following mpstat, cpu 2 is in 100% kernel usage, but no syscalls and no interrupts. CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl 0 0 0 0 300 100 0 0 1 0 0 0 0 0 0 100 1 14 0 0 134 68 134 1

...dladm/common/libdllink.h usr/src/lib/libdladm/common/libdlstat.c usr/src/lib/libdladm/common/libdlstat.h usr/src/lib/libdladm/common/libdlvlan.c usr/src/lib/libdladm/common/libdlvlan.h usr/src/lib/libdladm/common/libdlvnic.c usr/src/lib/libdladm/common/libdlvnic.h usr/src/lib/libdladm/common/linkprop.c usr/src/lib/libdladm/common/llib-ldladm usr/src/lib/libdladm/common/mapfile-vers usr/src/lib/libdladm/common/propfuncs.c usr/src/lib/libdladm/common/usage.c usr/src/lib/libfdisk/Makefile usr/src/lib/libfdisk/i386/Makefile usr/src/lib/libfdisk/i386/libfdisk.c usr/src/lib/libfdisk/i386/libf...

Hi Folks, I have a snv_105 sxce host that I just can''t get to work as expected with crossbow + zones. My test host persephone, is a virtual machine running under VMware ESXi 3.5, with 2 virtual network cards (e1000), all on the same flat network/subnet. It started life just 2 days ago with a clean install of snv_95, and I LUed to 105 yesterday. To rule out any sharing issue, the first