From: "ganeshkumar" <ganeshkumar@signal-networks.com>
To: <Linuxppc-dev@ozlabs.org>
Subject: System RAM requirement for PBX - Router Application product
Date: Mon, 19 Sep 2005 10:03:38 +0530 [thread overview]
Message-ID: <001901c5bcd3$4e181690$0d01a8c0@signet> (raw)
Dear All,
I'm working on MPC860P with 8MB of FLash ROM and 16MB of RAM
on our system running Mvista Linux. Our Product is an Integrated Access
Device
with the following features built in:
1) ISDN PRI on E1 interface with 15 channels for Voice & 15
Channels for Data
2) LAN to WAN Router and vice versa, serving Internet users on
the LAN side.
3) Built in PABx functionality serving upto 60 extensions
4) Embedded mySQL database for Call details and Records,
5) An IDE interface supporting a 80GB HDD
6) Web server for configuration (Boa)
So for a product with the above configuration/features , what is the minimum
amount memory that is needed to run without any flaws?
Currently we have 8MB Flash, 16MB SD-RAM with MPC860P running @ 40MHz
Is 16MB SD-RAM enough for this type of an Application? or we need to
increase our SD-RAM size?
Thanks in Advance!
Thanks & Best regards,
Ganesh
reply other threads:[~2005-09-19 4:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='001901c5bcd3$4e181690$0d01a8c0@signet' \
--to=ganeshkumar@signal-networks.com \
--cc=Linuxppc-dev@ozlabs.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