From owner-freebsd-hackers@FreeBSD.ORG Wed Dec 26 22:19:31 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 355C417C for ; Wed, 26 Dec 2012 22:19:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) by mx1.freebsd.org (Postfix) with ESMTP id B66888FC08 for ; Wed, 26 Dec 2012 22:19:30 +0000 (UTC) Received: by mail-wg0-f49.google.com with SMTP id 15so3963223wgd.28 for ; Wed, 26 Dec 2012 14:19:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=gPkLX25wf3ImJT3AFoyF38wOuhdfRsCHt6gBr17hu0Y=; b=Udu2H0KPdtSy4M+hwlAUGttkutFR/dMugwXR6v8M/ESYFLNvcy7ZyQBKQAjtQzCCBp Rx7lQ2lHWAtCpptFi+I5C6nM58Lvo0peTe1kzWIj1R6a/w8brt0J2+897FIz1e41FX1d qqhCvm5lIGdUL6mndzk6pWbjgfHmGei22OwRRbY7qaFBkDJwWOK/2S9MJSF4bJjBzuFv /of0cBFh2uX6oJN8TPIq3iU1B17UkWUP9pHSR4l12ZwSx5iJzlnhBMN2wWfL6fXGc4Te MOwj1WT6Rg1TZC/XC5uvYPZjUh1xJHTVLj9GxRAGHsn235XUcD7uRcSNRHP01o28Sf9p ndRA== MIME-Version: 1.0 Received: by 10.180.33.44 with SMTP id o12mr37972632wii.28.1356560364207; Wed, 26 Dec 2012 14:19:24 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.217.57.9 with HTTP; Wed, 26 Dec 2012 14:19:24 -0800 (PST) In-Reply-To: <20121226084805.91840@gmx.com> References: <20121226084805.91840@gmx.com> Date: Wed, 26 Dec 2012 14:19:24 -0800 X-Google-Sender-Auth: qg_bM52TN853kXcUoiGKvpSYqmo Message-ID: Subject: Re: FreeBSD for serious performance? From: Adrian Chadd To: Dieter BSD Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Dec 2012 22:19:31 -0000 Hm, can you come up with a reproducable scenario where this happening? A lot of times the issues with disk drivers being upset is due to "bad" or "incorrectly seated" SATA cables. We're willing to help you out if you're willing to delve into the driver. Just ask questions about how it works and you'll likely get help :) Adrian