netdev - Re: [PATCH][BONDING] Add max

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4405.1204311836@death>
Date:	Fri, 29 Feb 2008 11:03:56 -0800
From:	Jay Vosburgh <fubar@...ibm.com>
To:	Phil Oester <kernel@...uxace.com>
cc:	netdev@...r.kernel.org
Subject: Re: [PATCH][BONDING] Add max_bonds kernel parameter 


Phil Oester <kernel@...uxace.com> wrote:
[...]
>    The bonding driver (and initscripts) seem to assume everyone loads bonding
>    as a module.  So when compiled into the kernel, changing the max_bonds
>    parameter can only be done in the source code.

	The kernel should already handle options for compiled-in
modules.  For bonding, you'd put something like "bonding.max_bonds=3" on
the kernel boot line.  No need to patch bonding for this.  This is
described in Documentation/kernel-parameters.txt (right at the top).

	On your other patch, I don't see a big issue with allowing
max_bonds to be zero; I'll have a look at the details and test it out.

	-J

---
	-Jay Vosburgh, IBM Linux Technology Center, fubar@...ibm.com
--
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