From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Performance leaks with passive network interface cards
Date: Wed, 15 Feb 2012 11:59:53 +0100 [thread overview]
Message-ID: <0ced38252da16911f6de721b2cd0d9a3@mail01.ipfire.org> (raw)
In-Reply-To: <4F3B5EF9.70303@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2079 bytes --]
On Wed, 15 Feb 2012 08:30:01 +0100, Daniel Weismüller
<whytea(a)ipfire.org> wrote:
> Hey it's a wiki. Everyone could change things. So if you find
> something feel free to change it. ;)
I would recommend that you do the changes.
>
> btw. I don't know which vendor provide their own drivers.
You can find it on the MAINTAINERS file from the source code
of the Linux kernel.
Michael
>
> Am 14.02.2012 20:09, schrieb Michael Tremer:
>> Hi,
>>
>> I would like to see the "we recommend" message changed. It is much
>> better to write "which hardware is worth a recommendation" because there
>> is no "we".
>>
>> An also not so good point is the table at the bottom of the page. It
>> would be much better to add this information to the table over here
>> (http://wiki.ipfire.org/en/hardware/networking). It is not very easy to
>> maintain redundant information and it is also not very easy for the user
>> to join all this information together. You know what I mean...
>>
>> Another side node would also be interesting. You should consider adding
>> this: Vendors of hardware with controller chips provide their own
>> drivers in the kernel (Intel, etc.). Most of the cheaper ones do not and
>> so the quality is not as good as the first ones.
>>
>> Michael
>>
>> On Tue, 2012-02-14 at 19:10 +0100, WhyTea wrote:
>>> Hi again!
>>>
>>> I've imported the german and the english version into the wiki.
>>>
>>> http://wiki.ipfire.org/de/hardware/passivenics
>>> http://wiki.ipfire.org/en/hardware/passivenics
>>>
>>> Please take a look.
>>>
>>> - Daniel
>>> _______________________________________________
>>> Documentation mailing list
>>> Documentation(a)lists.ipfire.org
>>> http://lists.ipfire.org/mailman/listinfo/documentation
>> _______________________________________________
>> Documentation mailing list
>> Documentation(a)lists.ipfire.org
>> http://lists.ipfire.org/mailman/listinfo/documentation
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
prev parent reply other threads:[~2012-02-15 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 18:10 WhyTea
2012-02-14 19:09 ` Michael Tremer
2012-02-15 7:30 ` Daniel Weismüller
2012-02-15 10:59 ` Michael Tremer [this message]
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=0ced38252da16911f6de721b2cd0d9a3@mail01.ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=documentation@lists.ipfire.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