From owner-freebsd-current@FreeBSD.ORG Mon Oct 19 21:14:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1756106566C for ; Mon, 19 Oct 2009 21:14:08 +0000 (UTC) (envelope-from kalinoj1@iem.pw.edu.pl) Received: from volt.iem.pw.edu.pl (volt.iem.pw.edu.pl [194.29.146.3]) by mx1.freebsd.org (Postfix) with ESMTP id 742FC8FC16 for ; Mon, 19 Oct 2009 21:14:08 +0000 (UTC) Received: from [192.168.1.157] (chello087207124173.chello.pl [87.207.124.173]) (Authenticated sender: kalinoj1) by volt.iem.pw.edu.pl (Postfix) with ESMTPSA id 93CC7A66917 for ; Mon, 19 Oct 2009 22:55:16 +0200 (CEST) Message-ID: <4ADCD233.1070302@iem.pw.edu.pl> Date: Mon, 19 Oct 2009 22:55:15 +0200 From: Jedrzej Kalinowski User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: clamav-milter devel-20090930-exp at volt.iem.pw.edu.pl X-Virus-Status: Clean X-Mailman-Approved-At: Mon, 19 Oct 2009 21:33:03 +0000 Subject: Many tftp requests for each kernel and module file during DISKLESS boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2009 21:14:09 -0000 Hello, I work with a freebsd-current DISKLESS boot setup at my university and try to make the diskless boot as fast as possible. I was wondering why my tftp log of a machine boot process looks like this: ... Oct 19 20:12:14 bsd in.tftpd[45140]: RRQ from xxx filename /boot/loader.conf.local Oct 19 20:12:14 bsd in.tftpd[45141]: RRQ from xxx filename /boot/kernel/kernel Oct 19 20:12:14 bsd in.tftpd[45142]: RRQ from xxx filename /boot/kernel/kernel Oct 19 20:12:14 bsd in.tftpd[45143]: RRQ from xxx filename /boot/kernel/kernel ... There are three requests for a kernel file and even more requests for modules when they get loaded. I added some additional output in loader files to trace the requests and now I see (when loading a kernel) that the file is tried to get loaded in elfN(loadfile) functions found in source files /usr/src/boot/common/load_elf.c and /usr/src/boot/common/load_elf_obj.c with no success at first, than it is successfully loaded by load_elf.c. Each load attempt results in tftp request being issued to the server. My question is - is there a simple way of getting rid of these requests? Are there any plans to include some sort of local caching in loader? I think that the way it works now is not the most optimal one, because of redundant tftp RRQs. Regards, Jędrzej Kalinowski