From: Asfand Yar Qazi <ay1204@qazi.f2s.com>
To: linux-kernel@vger.kernel.org
Subject: Re: How's the nforce4 support in Linux?
Date: Thu, 24 Mar 2005 10:11:16 +0000 [thread overview]
Message-ID: <42429244.1070903@qazi.f2s.com> (raw)
In-Reply-To: <3Lxis-5a0-27@gated-at.bofh.it>
Asfand Yar Qazi wrote:
> Arjan van de Ven wrote:
>
>>> * "hardware firewall" -- sounds silly. Pretty sure Linux doesn't
>>> support
>>> it in any case.
>>>
>>
>>
>> probably just one of those things implemented in the binary drivers in
>> software, just like the "hardware" IDE raid is most of the time (3ware
>> being the positive exception there)
>>
>
> http://www.neoseeker.com/Articles/Hardware/Previews/nvnforce4/3.html
>
> You're right there - some semi-hardware support combined with drivers
> apparently result in lower CPU usage that software firewalls. Apparently.
>
> Actually, these people like it:
> http://www.bjorn3d.com/read.php?cID=712&pageID=1096
>
> However one feature that you can't laugh at is the fact that it can be
> made to block packets in the span of time between the OS being loaded
> up, and the "real" firewall coming up. This small time span
> theoretically leaves the PC vulnerable, so I think this is the only use
> for "ActiveAmor Firewall".
>
> However, this doesn't answer my original question (which I suppose I
> should have made clearer): can I get SATA II NCQ support in Linux with
> an nForce 4 chipset?
>
>
Argh already been answered. Another question: which add-in SATA RAID
boards (preferably in PCI Express flavour) support NCQ fully and will
be fully supported in Linux?
next parent reply other threads:[~2005-03-24 10:04 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3Lxis-5a0-29@gated-at.bofh.it>
[not found] ` <3Lxis-5a0-31@gated-at.bofh.it>
[not found] ` <3Lxis-5a0-33@gated-at.bofh.it>
[not found] ` <3Lxis-5a0-27@gated-at.bofh.it>
2005-03-24 10:11 ` Asfand Yar Qazi [this message]
[not found] ` <3LxBD-5wd-9@gated-at.bofh.it>
2005-03-24 10:33 ` [OT] " Asfand Yar Qazi
2005-03-24 16:43 ` Lennart Sorensen
2005-03-24 18:05 ` Asfand Yar Qazi
2005-03-26 16:01 Chuck
2005-03-26 15:19 ` Arjan van de Ven
2005-03-26 17:32 ` Marcin Dalecki
2005-03-27 12:26 ` Chuck
2005-04-02 23:55 ` Julien Wajsberg
-- strict thread matches above, loose matches on Subject: below --
2005-03-25 22:59 Julien Wajsberg
2005-03-25 23:14 ` Lee Revell
2005-03-26 0:38 ` Julien Wajsberg
2005-03-26 0:48 ` Lee Revell
2005-03-29 18:58 ` Tomasz Torcz
2005-03-29 20:40 ` Lee Revell
2005-03-30 15:00 ` Tomasz Torcz
2005-03-30 16:45 ` Lennart Sorensen
2005-03-30 19:19 ` Martin Schlemmer
2005-03-30 21:01 ` Lee Revell
2005-03-31 5:58 ` Martin Schlemmer
2005-03-25 23:20 ` Lee Revell
2005-03-26 0:17 ` Julien Wajsberg
2005-03-26 14:13 ` Michal Schmidt
2005-03-29 6:47 ` Julien Wajsberg
2005-03-25 23:21 ` Lee Revell
2005-03-25 23:41 ` Julien Wajsberg
2005-04-05 13:42 ` Julien Wajsberg
2005-04-05 14:10 ` Richard B. Johnson
2005-04-05 22:58 ` Julien Wajsberg
2005-04-06 11:41 ` Richard B. Johnson
2005-04-06 16:02 ` Bartlomiej Zolnierkiewicz
2005-04-10 23:43 ` Julien Wajsberg
2005-04-10 23:27 ` Julien Wajsberg
2005-03-25 9:37 Chuck Ebbert
[not found] <3LwFC-4Ko-15@gated-at.bofh.it>
[not found] ` <3LwYW-4Xx-11@gated-at.bofh.it>
[not found] ` <3LwYZ-4Xx-25@gated-at.bofh.it>
2005-03-24 10:00 ` Asfand Yar Qazi
2005-03-24 10:11 ` Arjan van de Ven
2005-03-24 16:29 ` Lennart Sorensen
2005-03-24 16:41 ` Raphael Jacquot
2005-03-24 20:41 ` Jeff Garzik
2005-03-25 2:15 ` Robert Hancock
2005-03-25 2:40 ` Lee Revell
2005-03-24 9:20 Asfand Yar Qazi
2005-03-24 9:30 ` Jeff Garzik
2005-03-24 9:34 ` Arjan van de Ven
2005-03-24 10:03 ` Tupshin Harper
2005-03-24 16:27 ` Lennart Sorensen
2005-03-24 21:01 ` Jeff Garzik
2005-03-28 15:31 ` Andi Kleen
2005-03-30 19:42 ` Jeff Garzik
2005-03-30 20:17 ` Indrek Kruusa
2005-03-30 20:25 ` Jeff Garzik
2005-03-30 20:48 ` Indrek Kruusa
2005-03-30 21:06 ` Francois Romieu
2005-03-30 21:47 ` Jeff Garzik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42429244.1070903@qazi.f2s.com \
--to=ay1204@qazi.f2s.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®