From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-AntiVirus: Checked by Dr.Web [version: 4.32b, engine: 4.32b, virus records: 77189, updated: 9.06.2005] Date: Sat, 18 Mar 2006 08:07:05 +0300 From: rs X-Mailer: The Bat! (v3.0) Professional Organization: sstu X-Priority: 3 (Normal) Message-ID: <1774292408.20060318080705@sstu.ru> To: ALT Linux Community In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Subject: Re: [Comm] eth0: Too much work X-BeenThere: community@lists.altlinux.org X-Mailman-Version: 2.1.7 Precedence: list Reply-To: rs , ALT Linux Community List-Id: ALT Linux Community List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Mar 2006 05:07:07 -0000 Archived-At: List-Archive: List-Post: Здравствуйте, Artem. Вы писали 17 марта 2006 г., 17:23:19: > Имею в логах > eth0: Too much work at interrupt, status=0x0004 > Google молчит. > Это о чём? я поднимал эту тему. во что мне ответили про max_interrupt_work: This option selects the maximum amount of work han- dled during each interrupt. Each received packet counts as one unit of work, as does updating statistics counters and handling errors. The default value of 32 should only need to be increased on very slow machines. An occasional "too much work in interrupt" message is not a prob- lem. ____________________________ С уважением, системный администратор СГТУ, каф."Системотехника" AND ЗАО "Тесар-СО", Егоров Стас ICQ:270805968 mailto:rs@sstu.ru