linux-kernel - dhcp-based netboot over jumbo-frame network?

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-next>] [day] [month] [year] [list]

Message-ID: <49DCE470.9060109@nortel.com>
Date:	Wed, 08 Apr 2009 11:52:48 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	linux-kernel@...r.kernel.org,
	Linux Network Development list <netdev@...r.kernel.org>
Subject: dhcp-based netboot over jumbo-frame network? 

Hi all,

We have an existing system that loads a bare kernel using tftp, then 
mounts a rootfs via NFS.  The wrinkle is that this is on a jumbo-frame 
enabled network, so somehow the MTU needs to be set before mounting the 
rootfs.

In a previous version we patched ipconfig.c to support the DHCP option 
to specify the MTU value, but I'm wondering about the "proper" way to do 
this on current kernels.

I suppose the obvious answer would be initramfs.  The downsides to that 
solution are that it would increase the size of the kernel file, and we 
would need to change the existing build system.  In the face of a small 
patch to ipconfig, it's not a very attractive solution.

Looking forward to your responses.

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/