From owner-freebsd-drivers@FreeBSD.ORG Sun Mar 18 22:56:34 2012 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2EC11106566C for ; Sun, 18 Mar 2012 22:56:34 +0000 (UTC) (envelope-from dieterbsd@engineer.com) Received: from mailout-us.gmx.com (mailout-us.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id CE90C8FC08 for ; Sun, 18 Mar 2012 22:56:33 +0000 (UTC) Received: (qmail 18759 invoked by uid 0); 18 Mar 2012 22:56:33 -0000 Received: from 67.206.186.200 by rms-us004.v300.gmx.net with HTTP Content-Type: text/plain; charset="utf-8" Date: Sun, 18 Mar 2012 18:56:29 -0400 From: "Dieter BSD" Message-ID: <20120318225630.155070@gmx.com> MIME-Version: 1.0 To: freebsd-hackers@freebsd.org,freebsd-drivers@freebsd.org X-Authenticated: #74169980 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: SQ0Ub/dd3zOlNR3dAHAhK4h+IGRvb4AB Cc: Subject: Reigning in disk cache buffer hogs X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Mar 2012 22:56:34 -0000 amd64 4 GiB nVidia nForce CK804 (aka nforce4-ultra), SiI3132, JMB363 sata disks FreeBSD 8.2 FFS/SU Problem: I/O to one disk can fill up the disk buffer cache, starving other processes of disk I/O.  If the other processes are logging real time data (from a closed source "black box"), then data is lost.  Each process has its own private disk to minimise latency due to seeking and such, but that isn't sufficient to prevent the problem. It is always the onboard nforce4-ultra controller that causes the problem. The expansion card controllers never cause the problem. The onboard nforce4-ultra controller is supported by ata(4). The expansion card controllers are supported by ahci(4) and siis(4). The onboard nforce4-ultra controller is much faster than the expansion card controllers, except that ata doesn't support NCQ, so the nforce has a serious bottleneck writing. Is there something about NCQ other than the obvious performance improvement that would explain why the NCQ controllers never have the problem? What sort of miracle would it take to get NCQ support for the nforce4-ultra controller?  Linix has had NCQ support since 2006. Is there some knob to control reserving a few buffers per disk to prevent one disk from hogging all the buffer cache? From owner-freebsd-drivers@FreeBSD.ORG Mon Mar 19 15:25:47 2012 Return-Path: Delivered-To: drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01B39106566B; Mon, 19 Mar 2012 15:25:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C9E178FC1F; Mon, 19 Mar 2012 15:25:46 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 7C82946B17; Mon, 19 Mar 2012 11:25:46 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DEDA9B960; Mon, 19 Mar 2012 11:25:45 -0400 (EDT) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Mon, 19 Mar 2012 09:24:06 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <88AB8EB2D3F1D249AE07FAFFF17A396F0384C3956A@HZU1EXCH02.hq.exar.com> In-Reply-To: <88AB8EB2D3F1D249AE07FAFFF17A396F0384C3956A@HZU1EXCH02.hq.exar.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203190924.06912.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 19 Mar 2012 11:25:46 -0400 (EDT) Cc: Yong Fan , "drivers@FreeBSD.org" Subject: Re: How can I decide whether my code is running in interrupt context or not? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2012 15:25:47 -0000 On Thursday, March 15, 2012 10:06:13 pm Yong Fan wrote: > Hi all, > > In Linux, I can use in_interrupt() function. > FreeBSD has such a similar kernel function for drivers? Hmm, we do not, though the only part of your driver that can run in primary interrupt context is an interrupt filter. If you mean interrupt-thread context (i.e. when sleeping is not permitted), then that would apply to your normal interrupt handler and any callout routines that you have. -- John Baldwin From owner-freebsd-drivers@FreeBSD.ORG Mon Mar 19 15:25:47 2012 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 01B39106566B; Mon, 19 Mar 2012 15:25:47 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id C9E178FC1F; Mon, 19 Mar 2012 15:25:46 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [96.47.65.170]) by cyrus.watson.org (Postfix) with ESMTPSA id 7C82946B17; Mon, 19 Mar 2012 11:25:46 -0400 (EDT) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DEDA9B960; Mon, 19 Mar 2012 11:25:45 -0400 (EDT) From: John Baldwin To: freebsd-drivers@freebsd.org Date: Mon, 19 Mar 2012 09:24:06 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p10; KDE/4.5.5; amd64; ; ) References: <88AB8EB2D3F1D249AE07FAFFF17A396F0384C3956A@HZU1EXCH02.hq.exar.com> In-Reply-To: <88AB8EB2D3F1D249AE07FAFFF17A396F0384C3956A@HZU1EXCH02.hq.exar.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203190924.06912.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 19 Mar 2012 11:25:46 -0400 (EDT) Cc: Yong Fan , "drivers@FreeBSD.org" Subject: Re: How can I decide whether my code is running in interrupt context or not? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Mar 2012 15:25:47 -0000 On Thursday, March 15, 2012 10:06:13 pm Yong Fan wrote: > Hi all, > > In Linux, I can use in_interrupt() function. > FreeBSD has such a similar kernel function for drivers? Hmm, we do not, though the only part of your driver that can run in primary interrupt context is an interrupt filter. If you mean interrupt-thread context (i.e. when sleeping is not permitted), then that would apply to your normal interrupt handler and any callout routines that you have. -- John Baldwin From owner-freebsd-drivers@FreeBSD.ORG Tue Mar 20 01:43:29 2012 Return-Path: Delivered-To: drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF4111065670; Tue, 20 Mar 2012 01:43:29 +0000 (UTC) (envelope-from yong.fan@exar.com) Received: from smtp1.exar.com (webmail.exar.com [204.154.183.83]) by mx1.freebsd.org (Postfix) with ESMTP id CEDA08FC14; Tue, 20 Mar 2012 01:43:29 +0000 (UTC) Received: from HZU1EXCH02.hq.exar.com (172.18.10.52) by FRE1-CAS.hq.exar.com (10.127.1.162) with Microsoft SMTP Server (TLS) id 8.1.436.0; Mon, 19 Mar 2012 18:43:29 -0700 Received: from HZU1EXCH02.hq.exar.com ([fe80::5528:f080:2385:1c90]) by HZU1EXCH02.hq.exar.com ([fe80::5528:f080:2385:1c90%13]) with mapi; Tue, 20 Mar 2012 09:43:25 +0800 From: Yong Fan To: John Baldwin , "freebsd-drivers@freebsd.org" Date: Tue, 20 Mar 2012 09:43:23 +0800 Thread-Topic: How can I decide whether my code is running in interrupt context or not? Thread-Index: Ac0F5JE1lnduUOCoRHuQCf6FFaeaPQAVi87w Message-ID: <88AB8EB2D3F1D249AE07FAFFF17A396F0384C398AC@HZU1EXCH02.hq.exar.com> References: <88AB8EB2D3F1D249AE07FAFFF17A396F0384C3956A@HZU1EXCH02.hq.exar.com> <201203190924.06912.jhb@freebsd.org> In-Reply-To: <201203190924.06912.jhb@freebsd.org> Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, zh-CN Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "drivers@FreeBSD.org" Subject: RE: How can I decide whether my code is running in interrupt context or not? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 01:43:30 -0000 Thanks your warm reply. I see. Thanks Yongfan -----Original Message----- From: John Baldwin [mailto:jhb@freebsd.org] Sent: Monday, March 19, 2012 7:24 AM To: freebsd-drivers@freebsd.org Cc: Yong Fan; drivers@FreeBSD.org Subject: Re: How can I decide whether my code is running in interrupt conte= xt or not? On Thursday, March 15, 2012 10:06:13 pm Yong Fan wrote: > Hi all, > > In Linux, I can use in_interrupt() function. > FreeBSD has such a similar kernel function for drivers? Hmm, we do not, though the only part of your driver that can run in primary interrupt context is an interrupt filter. If you mean interrupt-thread context (i.e. when sleeping is not permitted), then that would apply to you= r normal interrupt handler and any callout routines that you have. -- John Baldwin The information and any attached documents contained in this message may be confidential and/or legally privileged. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender immediately by return e-mail and destroy all copies of the original message. From owner-freebsd-drivers@FreeBSD.ORG Tue Mar 20 01:43:29 2012 Return-Path: Delivered-To: freebsd-drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF4111065670; Tue, 20 Mar 2012 01:43:29 +0000 (UTC) (envelope-from yong.fan@exar.com) Received: from smtp1.exar.com (webmail.exar.com [204.154.183.83]) by mx1.freebsd.org (Postfix) with ESMTP id CEDA08FC14; Tue, 20 Mar 2012 01:43:29 +0000 (UTC) Received: from HZU1EXCH02.hq.exar.com (172.18.10.52) by FRE1-CAS.hq.exar.com (10.127.1.162) with Microsoft SMTP Server (TLS) id 8.1.436.0; Mon, 19 Mar 2012 18:43:29 -0700 Received: from HZU1EXCH02.hq.exar.com ([fe80::5528:f080:2385:1c90]) by HZU1EXCH02.hq.exar.com ([fe80::5528:f080:2385:1c90%13]) with mapi; Tue, 20 Mar 2012 09:43:25 +0800 From: Yong Fan To: John Baldwin , "freebsd-drivers@freebsd.org" Date: Tue, 20 Mar 2012 09:43:23 +0800 Thread-Topic: How can I decide whether my code is running in interrupt context or not? Thread-Index: Ac0F5JE1lnduUOCoRHuQCf6FFaeaPQAVi87w Message-ID: <88AB8EB2D3F1D249AE07FAFFF17A396F0384C398AC@HZU1EXCH02.hq.exar.com> References: <88AB8EB2D3F1D249AE07FAFFF17A396F0384C3956A@HZU1EXCH02.hq.exar.com> <201203190924.06912.jhb@freebsd.org> In-Reply-To: <201203190924.06912.jhb@freebsd.org> Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, zh-CN Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "drivers@FreeBSD.org" Subject: RE: How can I decide whether my code is running in interrupt context or not? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Mar 2012 01:43:30 -0000 Thanks your warm reply. I see. Thanks Yongfan -----Original Message----- From: John Baldwin [mailto:jhb@freebsd.org] Sent: Monday, March 19, 2012 7:24 AM To: freebsd-drivers@freebsd.org Cc: Yong Fan; drivers@FreeBSD.org Subject: Re: How can I decide whether my code is running in interrupt conte= xt or not? On Thursday, March 15, 2012 10:06:13 pm Yong Fan wrote: > Hi all, > > In Linux, I can use in_interrupt() function. > FreeBSD has such a similar kernel function for drivers? Hmm, we do not, though the only part of your driver that can run in primary interrupt context is an interrupt filter. If you mean interrupt-thread context (i.e. when sleeping is not permitted), then that would apply to you= r normal interrupt handler and any callout routines that you have. -- John Baldwin The information and any attached documents contained in this message may be confidential and/or legally privileged. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender immediately by return e-mail and destroy all copies of the original message. From owner-freebsd-drivers@FreeBSD.ORG Fri Mar 23 03:21:18 2012 Return-Path: Delivered-To: drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A2AB5106564A for ; Fri, 23 Mar 2012 03:21:18 +0000 (UTC) (envelope-from yong.fan@exar.com) Received: from smtp1.exar.com (webmail.exar.com [204.154.183.83]) by mx1.freebsd.org (Postfix) with ESMTP id 837028FC14 for ; Fri, 23 Mar 2012 03:21:18 +0000 (UTC) Received: from HZU1EXCH02.hq.exar.com (172.18.10.52) by FRE1-CAS.hq.exar.com (10.127.1.162) with Microsoft SMTP Server (TLS) id 8.1.436.0; Thu, 22 Mar 2012 20:21:16 -0700 Received: from HZU1EXCH02.hq.exar.com ([fe80::5528:f080:2385:1c90]) by HZU1EXCH02.hq.exar.com ([fe80::5528:f080:2385:1c90%13]) with mapi; Fri, 23 Mar 2012 11:21:13 +0800 From: Yong Fan To: "drivers@FreeBSD.org" Date: Fri, 23 Mar 2012 11:21:12 +0800 Thread-Topic: How can I decide the kernel version? Thread-Index: Ac0Io/9hTiR9pEXmTsCh8bjELhDUrg== Message-ID: <88AB8EB2D3F1D249AE07FAFFF17A396F0384CEF9AD@HZU1EXCH02.hq.exar.com> Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, zh-CN MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: How can I decide the kernel version? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 03:21:18 -0000 Hi all, How can I decide the kernel version? In linux, I can use LINUX_VERSION_CODE and KERNEL_VERSION(x,y,z). Does FreeBSD has such similar MACRO? Yongfan Thanks ________________________________ The information and any attached documents contained in this message may be confidential and/or legally privileged. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, dissemination, or reproduction is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender immediately by return e-mail and destroy all copies of the original message. From owner-freebsd-drivers@FreeBSD.ORG Fri Mar 23 04:24:55 2012 Return-Path: Delivered-To: drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4BD36106564A for ; Fri, 23 Mar 2012 04:24:55 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id CBB578FC16 for ; Fri, 23 Mar 2012 04:24:54 +0000 (UTC) Received: by wern13 with SMTP id n13so3152874wer.13 for ; Thu, 22 Mar 2012 21:24:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=kT9XbHOklKbfkQLgS8YaHHjbHwfwGzqEsi2J0ZjQzoY=; b=Kh55wZSSOCPUjNuZ+8mFgC+OF+rA9i29ZRYWR0erSPEWhEUM5k6f4qM4NTZkDSMBH4 11P9zYa8MB1MryYYOiPGFpIsrXZ0yeSjSoHPha9ZXCZCBXBLkc6AFP3nrdvgC3pjQlc7 eayi3JmbEyTq9T4trS99/NJYuw9sHVJFW02fg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=kT9XbHOklKbfkQLgS8YaHHjbHwfwGzqEsi2J0ZjQzoY=; b=GMecIKeoTclA4lpLV6uJ+EKwd2MbMhc2xwJBwL4JXSeJHI4SgTka0smcqnY4GdDslH JJs4O8zjr9vGSF1M0vPH5oEsiP4dL64jd5rm7j0Pxt7RI53BqKv9zqkwKbfuolbZ6qz3 iG41WsvWRJNV/0WDOWO9KNWFSS8+9jGtpf3L4O0g3IjE0RAQqvyCRpSJWEX2ZtQYoagC ov9yAbQqB3Eve4fEg8pm+VQNa3DRYIFjefFrkvEoI2kvKjQWfmexP2SOttkvexIwoEXG oBowpSpmsxzhj8tITVyFaBByNjslJRQ9e+QYXnH2LrTIMQc2qbYymga/+Sc27otDTQYV sVLA== Received: by 10.180.84.164 with SMTP id a4mr3161569wiz.2.1332476693748; Thu, 22 Mar 2012 21:24:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.63.4 with HTTP; Thu, 22 Mar 2012 21:24:23 -0700 (PDT) In-Reply-To: <88AB8EB2D3F1D249AE07FAFFF17A396F0384CEF9AD@HZU1EXCH02.hq.exar.com> References: <88AB8EB2D3F1D249AE07FAFFF17A396F0384CEF9AD@HZU1EXCH02.hq.exar.com> From: Eitan Adler Date: Fri, 23 Mar 2012 00:24:23 -0400 Message-ID: To: Yong Fan Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkfI1OHyIjTdsEt70k2XQMdHZ//NRMCGAAc1DDf2NIlvd1T5BnOop+Ni6kGy76KPN0hpMcb Cc: "drivers@FreeBSD.org" Subject: Re: How can I decide the kernel version? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 04:24:55 -0000 On Thu, Mar 22, 2012 at 11:21 PM, Yong Fan wrote: > Hi all, > > How can I decide the kernel version? > In linux, I can use LINUX_VERSION_CODE and KERNEL_VERSION(x,y,z). > Does FreeBSD has such similar MACRO? __FreeBSD_version ? http://www.freebsd.org/doc/en/books/porters-handbook/book.html#FREEBSD-VERSIONS -- Eitan Adler From owner-freebsd-drivers@FreeBSD.ORG Fri Mar 23 10:48:37 2012 Return-Path: Delivered-To: drivers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6E8F5106566B for ; Fri, 23 Mar 2012 10:48:37 +0000 (UTC) (envelope-from yong.fan@exar.com) Received: from smtp1.exar.com (webmail.exar.com [204.154.183.83]) by mx1.freebsd.org (Postfix) with ESMTP id 5027E8FC0A for ; Fri, 23 Mar 2012 10:48:37 +0000 (UTC) Received: from HZU1EXCH02.hq.exar.com (172.18.10.52) by FRE1-CAS.hq.exar.com (10.127.1.162) with Microsoft SMTP Server (TLS) id 8.1.436.0; Fri, 23 Mar 2012 03:48:30 -0700 Received: from HZU1EXCH02.hq.exar.com ([fe80::5528:f080:2385:1c90]) by HZU1EXCH02.hq.exar.com ([fe80::5528:f080:2385:1c90%13]) with mapi; Fri, 23 Mar 2012 18:48:26 +0800 From: Yong Fan To: Eitan Adler Date: Fri, 23 Mar 2012 18:48:24 +0800 Thread-Topic: How can I decide the kernel version? Thread-Index: Ac0IrOiP7Us4YnTjSlOa8gdcbbsTYwANYdeQ Message-ID: <88AB8EB2D3F1D249AE07FAFFF17A396F0384CEFAB8@HZU1EXCH02.hq.exar.com> References: <88AB8EB2D3F1D249AE07FAFFF17A396F0384CEF9AD@HZU1EXCH02.hq.exar.com> In-Reply-To: Accept-Language: en-US, zh-CN Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, zh-CN Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 MIME-Version: 1.0 Cc: "drivers@FreeBSD.org" Subject: RE: How can I decide the kernel version? X-BeenThere: freebsd-drivers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Writing device drivers for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 10:48:37 -0000 X19GcmVlQlNEX3ZlcnNpb24gY2FuIHdvcmsuDQpUaGFua3MNCg0KWW9uZ2Zhbg0KDQotLS0tLU9y aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogRWl0YW4gQWRsZXIgW21haWx0bzpsaXN0c0BlaXRh bmFkbGVyLmNvbV0NClNlbnQ6IFRodXJzZGF5LCBNYXJjaCAyMiwgMjAxMiAxMDoyNCBQTQ0KVG86 IFlvbmcgRmFuDQpDYzogZHJpdmVyc0BGcmVlQlNELm9yZw0KU3ViamVjdDogUmU6IEhvdyBjYW4g SSBkZWNpZGUgdGhlIGtlcm5lbCB2ZXJzaW9uPw0KDQpPbiBUaHUsIE1hciAyMiwgMjAxMiBhdCAx MToyMSBQTSwgWW9uZyBGYW4gPHlvbmcuZmFuQGV4YXIuY29tPiB3cm90ZToNCj4gSGkgYWxsLA0K Pg0KPiBIb3cgY2FuIEkgZGVjaWRlIHRoZSBrZXJuZWwgdmVyc2lvbj8NCj4gSW4gbGludXgsIEkg Y2FuIHVzZSBMSU5VWF9WRVJTSU9OX0NPREUgYW5kIEtFUk5FTF9WRVJTSU9OKHgseSx6KS4NCj4g RG9lcyBGcmVlQlNEIGhhcyBzdWNoIHNpbWlsYXIgTUFDUk8/DQoNCiBfX0ZyZWVCU0RfdmVyc2lv biA/DQpodHRwOi8vd3d3LmZyZWVic2Qub3JnL2RvYy9lbi9ib29rcy9wb3J0ZXJzLWhhbmRib29r L2Jvb2suaHRtbCNGUkVFQlNELVZFUlNJT05TDQoNCg0KLS0NCkVpdGFuIEFkbGVyDQoNClRoZSBp bmZvcm1hdGlvbiBhbmQgYW55IGF0dGFjaGVkIGRvY3VtZW50cyBjb250YWluZWQgaW4gdGhpcyBt ZXNzYWdlDQptYXkgYmUgY29uZmlkZW50aWFsIGFuZC9vciBsZWdhbGx5IHByaXZpbGVnZWQuICBU aGUgbWVzc2FnZSBpcw0KaW50ZW5kZWQgc29sZWx5IGZvciB0aGUgYWRkcmVzc2VlKHMpLiAgSWYg eW91IGFyZSBub3QgdGhlIGludGVuZGVkDQpyZWNpcGllbnQsIHlvdSBhcmUgaGVyZWJ5IG5vdGlm aWVkIHRoYXQgYW55IHVzZSwgZGlzc2VtaW5hdGlvbiwgb3INCnJlcHJvZHVjdGlvbiBpcyBzdHJp Y3RseSBwcm9oaWJpdGVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuICBJZiB5b3UgYXJlDQpub3QgdGhl IGludGVuZGVkIHJlY2lwaWVudCwgcGxlYXNlIGNvbnRhY3QgdGhlIHNlbmRlciBpbW1lZGlhdGVs eSBieQ0KcmV0dXJuIGUtbWFpbCBhbmQgZGVzdHJveSBhbGwgY29waWVzIG9mIHRoZSBvcmlnaW5h bCBtZXNzYWdlLg0K