netdev - bonding xmit

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANj2Ebfj+7R+wCK7jJennBN7_6THJGqs8FWSAPOv7BYYsR=u9w@mail.gmail.com>
Date:	Sat, 12 Nov 2011 21:55:42 -0500
From:	Simon Chen <simonchennj@...il.com>
To:	netdev@...r.kernel.org
Subject: bonding xmit_policy

Hi folks,

It looks like that there are three entries in xmit_policy (hashing for
deciding egress phy int) for bonded interfaces:

const struct bond_parm_tbl xmit_hashtype_tbl[] = {
{       "layer2",               BOND_XMIT_POLICY_LAYER2},
{       "layer3+4",             BOND_XMIT_POLICY_LAYER34},
{       "layer2+3",             BOND_XMIT_POLICY_LAYER23},
{       NULL,                   -1},
};


We can set the xmit_policy either at module initiation, or later via
/sys. However, this xmit_policy isn't really read anywhere. Are
different policies really implemented?

Thanks.
-Simon
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html