| To: | Jun Sun <jsun@mvista.com> |
|---|---|
| Subject: | Re: MIPS 64? |
| From: | Ralf Baechle <ralf@oss.sgi.com> |
| Date: | Sun, 19 May 2002 12:44:35 -0700 |
| Cc: | "Kevin D. Kissell" <kevink@mips.com>, Daniel Jacobowitz <dan@debian.org>, Matthew Dharm <mdharm@momenco.com>, Linux-MIPS <linux-mips@oss.sgi.com> |
| In-reply-to: | <3CE3E8BA.8080002@mvista.com>; from jsun@mvista.com on Thu, May 16, 2002 at 10:13:30AM -0700 |
| References: | <NEBBLJGMNKKEEMNLHGAIOEPPCGAA.mdharm@momenco.com> <20020515214818.GA1991@nevyn.them.org> <3CE2DA46.3070402@mvista.com> <007a01c1fca9$86e14f70$10eca8c0@grendel> <3CE3E8BA.8080002@mvista.com> |
| Sender: | owner-linux-mips@oss.sgi.com |
| User-agent: | Mutt/1.2.5.1i |
On Thu, May 16, 2002 at 10:13:30AM -0700, Jun Sun wrote: > BTW, I have been under the impression that demand for larger system RAM > mainly comes from large router/switches to store routing table. Does > anybody know on such systems whether the routing code runs in kernel or > user space and whether it requires all the memory space accessible at > the same time or can live with dynamically managed memory space? Kernel routing is more for the lower end systems; the highend systems use hardware assisted routing / switching where software only handles the boundary cases; such software might either live in user or in kernel space. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: MIPS 64?, Ralf Baechle |
|---|---|
| Next by Date: | Re: MIPS 64?, Matthew Dharm |
| Previous by Thread: | Re: MIPS 64?, Jun Sun |
| Next by Thread: | Re: MIPS 64?, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |