All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: jmerkey@comcast.net
Cc: William Lee Irwin III <wli@holomorphy.com>,
	Roland Dreier <roland@topspin.com>,
	linux-kernel@vger.kernel.org, jmerkey@drdos.com
Subject: Re: 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM)
Date: Thu, 26 Aug 2004 22:41:38 +0100	[thread overview]
Message-ID: <20040826214138.GA11336@redhat.com> (raw)
In-Reply-To: <082620042024.23755.412E47050006895C00005CCB2200751150970A059D0A0306@comcast.net>

On Thu, Aug 26, 2004 at 08:24:38PM +0000, jmerkey@comcast.net wrote:
 
 > What do you plan to do when the driver base becomes as 
 > large as the one in WIndows 2000/XP

There's a slew of drivers for ancient hardware in Linux that will /never/
be supported in Windows 2000/XP. Given we also support a majority of modern
hardware, chances are we're either comparable, or maybe even surpassing
Microsoft in terms of number of drivers shipped.

 > and you don't have enough memory to load all the drivers.

Since when do we load /all/ the drivers ? That would be silly.

 > Right now, iptables barfs even with 3GB of address space when you load up
 > about a dozen virtual network interfaces ?

I'll hazard a guess this has nothing whatsoever do to with address space sizes.

 > Microsoft had this same problem (only at a much sooner juncture in their
 > platform evolution) and went to VM support in the kernel
 > itself to increase virtual address space for kernel apps, file systems, and
 > drivers when thye hit the wall.    It's coming time to start thinking about
 > it.  

If we did stupid things like trying to load every single driver, maybe.
But we don't, so I think you're chasing ghosts.

		Dave


  parent reply	other threads:[~2004-08-26 22:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 20:24 1GB/2GB/3GB User Space Splitting Patch 2.6.8.1 (PSEUDO SPAM) jmerkey
2004-08-26 20:38 ` William Lee Irwin III
2004-08-26 21:41 ` Dave Jones [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-31 22:50 jmerkey
2004-08-30  5:56 jmerkey
2004-08-30 18:10 ` Randy.Dunlap
2004-08-30 18:28   ` Roland Dreier
2004-09-22 18:52   ` Timothy Miller
2004-09-22 18:51     ` Roland Dreier
2004-09-22 20:22       ` Timothy Miller
2004-09-27 14:55         ` Roland Dreier
2004-08-30  4:01 jmerkey
2004-08-30  4:35 ` Randy.Dunlap
2004-08-26 23:47 linux
2004-08-26 21:08 jmerkey
2004-08-26 21:43 ` William Lee Irwin III
2004-08-26  4:21 jmerkey
2004-08-26  4:33 ` William Lee Irwin III
2004-08-26  4:46   ` Roland Dreier
2004-08-26  4:49     ` William Lee Irwin III
2004-08-26  8:40       ` Ryan Cumming
2004-08-29 12:48       ` Alan Cox
2004-08-29 16:42         ` William Lee Irwin III
2004-08-29 15:45           ` Alan Cox
2004-08-29 17:00             ` William Lee Irwin III
2004-08-26  4:38 ` Martin J. Bligh
2004-08-26  4:42 ` Roland Dreier

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=20040826214138.GA11336@redhat.com \
    --to=davej@redhat.com \
    --cc=jmerkey@comcast.net \
    --cc=jmerkey@drdos.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@topspin.com \
    --cc=wli@holomorphy.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.