From: "H. Peter Anvin" <hpa@zytor.com>
To: Daniel Rodrick <daniel.rodrick@gmail.com>
Cc: Linux Newbie <linux-newbie@vger.kernel.org>,
kernelnewbies <kernelnewbies@nl.linux.org>,
linux-net@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Univeral Protocol Driver (using UNDI) in Linux
Date: Mon, 07 Aug 2006 09:49:42 -0700 [thread overview]
Message-ID: <44D76F26.9@zytor.com> (raw)
In-Reply-To: <292693080608070911g57ae1215qd994e03b9dd87b66@mail.gmail.com>
Daniel Rodrick wrote:
>
> Agreed. But still having a single driver for all the NICs would be
> simply GREAT for my setup, in which all the PCs will be booted using
> PXE only. So apart from performance / relilability issues, what are
> the technical roadblocks in this?
>
> I'm sure having a single driver for all the NICs is a feature cool
> enough to die for. Yes, it might have drawbacks like just pointed out
> by Peter, but surely a "single driver for all NIC" feature could prove
> to be great in some systems.
>
Assuming it works, which is questionable in my opinion.
> But since it does not already exist in the kernel, there must be some
> technical feasibility isse. Any ideas on this?
No, that's not the reason. The Intel code was ugly, and the limitations
made other people not want to spend any time hacking on it.
-hpa
next prev parent reply other threads:[~2006-08-07 16:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-07 10:39 Univeral Protocol Driver (using UNDI) in Linux Daniel Rodrick
2006-08-07 15:09 ` H. Peter Anvin
2006-08-07 16:11 ` Daniel Rodrick
2006-08-07 16:49 ` H. Peter Anvin [this message]
2006-08-08 5:13 ` Daniel Rodrick
2006-08-08 15:04 ` Alan Shieh
2006-08-10 8:18 ` Daniel Rodrick
2006-08-11 20:01 ` Alan Shieh
2006-08-10 20:59 ` Donald Becker
2006-08-10 21:08 ` H. Peter Anvin
2006-08-11 20:48 ` Alan Shieh
2006-08-08 16:35 ` H. Peter Anvin
2006-08-07 18:00 ` Jan Engelhardt
2006-08-07 18:15 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2006-09-28 9:59 Deepak Gupta
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=44D76F26.9@zytor.com \
--to=hpa@zytor.com \
--cc=daniel.rodrick@gmail.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-newbie@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