The original poster asked for BG not B5.
I'm too young or TOO OLD to remember BG very well so I don't recall the religous overtones.
but.. but.. it still lasts longer than M$Windows..
on
nVidia nForce
·
· Score: 1
closed source drivers, hopefully they will have a fix for that..
Re:A strange combination, to say the least.
on
nVidia nForce
·
· Score: 2
Just a minor correction..
NOT 128bit DDR memory:
nForce has two independent 64bit DDR memory buses, see..
http://www.anandtech.com/chipsets/showdoc.html?i =1 484&p=4
When both banks are are populated (with a 64bit DDR DIMM in each) you have a "virtual" 128bit bus. However, if the two banks are interleaved, you do get 100% boost in bandwidth.
Note: more bandwidth is not what limits 1+GHz PCs, its memory latency and system contention.
nForce is the 1st chipset to attempt to address the issue of contention while NOT increasing memory latencies.
Re:Memory interleaving
on
nVidia nForce
·
· Score: 5
nForce does not use memory interleaving, it uses a memory crossbar.
memory interleaving:
Interleaving of different banks of memory which are in SERIES.
+ shortens address line setup time for sequential memory access.
+ upto 30% more bandwidth (depending on type of memory FPS/EDO/SDRAM) when the cache line is double (or quadruple) of the bus width.
memory crossbar = Interleaving of banks of memory which are in PARALLEL.
+ parallel memory transactions (if each is for a different bank).
+ improvements are less deterministic, depends on which transactions can be parallelized.
+ does reduce memory contention, i.e. different devices (CPU, Video, Disk, NIC) wanting access to memory at the same time.
For multimedia type applications (read games, DVD playback) this is a big help.
nForce's twin-bank memory sub-system reminds me of the Amiga's twin bank memory sub-system.
Great so you have localized storage of different versions and possibly localized loading of different versions.
"your binary has to ask for a particular, or minimum, version of the dll"
So with XP M$ will finally "try" (its not out yet) to fix their F**K UP versioning. How long before the majority of apps are "AWARE" of this "innovative feature"? (hint proper version control has been taught in software engineering for over 10 years).
Do you know why XP has to have this?
otherwise.net becomes.not
Server has one version and the clients have other versions.
The Tutalin PIII is a redesign..
a) based on (www.tomshardware)'s article that a bigger brother will have 512KB of on-chip l2 cache (can't just stuff in more cache).
b) Intel minion's words..
http://www.pcworld.com/resource/printable/articl e/ 0,aid,42844,00.asp
From the processor design point of view dropping the microns does not automatically give you higher clock speeds. Your CPU has to be designed with enough stages to scale to higher clocks. A good reference for this point..
http://www.arstechnica.com/cpu/1q00/g4vsk7/g4vsk 7- 1.html
The copperMine 0.18 core was originally designed for 1.1GHz only (intel words, can't find a reference).
Re:This actually is the killer app...
on
PS2 As PC
·
· Score: 1
So will have a binary only kernel for the nForce?
If we are really good children (father know's best) nVidia may give us source for everything except the graphics card.
In either case, without good, open, graphics its not a open console spec.
Many peering agreements have clauses for charges based on usage differential, i.e..
How much of PSInet's bandwidth is used by C&W's traffic VERSUS how much of C&W's bandwidth is used by PSInet's traffic.
C&W can't expect to be paid for such charges so why continue to do business with PSInet?
Your head is stuck in the PCI specification manuals.
The reality is that *some* (possibly most) PCI devices..
a) from a hardware prespective don't like to share IRQ's
b) from a software prespective have crappy drivers that don't (for some devices can't) follow the specification close enough.
For any time critical application (video editing, server type stuff) shared IRQs can be a problem
I have not looked into Novell stuff for about 6months, but I think you are mistaken..
e-directory (your name NDS) is NDS that can run on NetwareOS, WinNT/2K and Linux..
a) On WinNT/2K it actually replaces domain/AD as the authenticator.
b) on Linux it replaces the password file by using PAM modules to redirect authentications to NDS
What you are thinking of is DirXML a directory synchronizing daemon that maps parts of AD to NDS and vice-versa. IMO it is the slickest software from Novell since Netware 3.11 came out.
You create the mapping of NDS schema to/from AD and you can tell it what part of (container / organizational unit) your NDS maps to what part of AD. You are still running two directories which are being synchronized at an interval you decide. What makes it kick ass is the schema and attributes synch is all visual, point and click.
Dude are you a troll or an artist that didn't get a contract?
Even before the internet/napster, big labels were milking the public and the artists..
a) FCC busted a group of the big ones for CD price fixing.
b) most of the contracts offerred to no-name artists were just short of "sell your soul" and/or "sell your soul and we own your life as an artist for the duration of the contract"
Even before the internet became big, the music industry combined with distribution and marketing channels were being described as a racket. (Think AOL-TimeWarner, content + distribution).
Factor in the mainstream success of "manufactured bands" (BackStreetBoys, NewKidsOnTheBlock, etc) and you have to ask yourself, IS THERE ANY PLACE/MEDIUM FOR REAL ARTISTS?
We have 64bit, 66MHz PCI RIGHT NOW.
http://www.serverworks.com/frames/prodHE_frame.h tm l
Yes its Intel only, but the PCI 64bit, 66MHz specification exists.
AMD:
Hopefully, 760MP will have support for at least 64bit 33MHz. Not sure about 64bit, 66MHz.
This is my 1st post so bare with me..
Yes Novell is no longer NOS market leaders, when they were, NOS meant file and print services. Now NOS means a lot more. Does this mean Netware is dead? Perhaps Netware is dead/ing (I do not think so), but Novell!=Netware.
Multiplatform NDS is Novell and their recent products reflect this.
1) What I have observed about organizations with IT departments..
If the IT group responsible for server services does not have close ties to the IT group responsible for desktop services, you are more likely to run *nix (if the admin is smart and the manager has balls) otherwise M$.
IF this is not the case and the two groups have close ties or are one then suddenly netware+NDS+ZenWorks is a compelling solution for file and print services. Now with NDS on linux and Solaris it is possible to have one login+password for each user for ALL services.
2) I work in a "Netware Shop", we are not committed to Novell, (we only run Netware) email is unix, web is unix, Oracle is on unix. Each system is a separate userID+password. Yes we started with Netware 2.x to 3.x to 4.11. We are contemplating moving to nw5.x. For over a year I have been researching our upgrade options (for FILE SERVICES, to replace Netware 4.xx)
One of the key requirements is a Journaling File System.
NW5.x has NSS. A journaling filesystem which now has quota support (a requirement).
Linux has ReiserFS. It works great, but the lack of VMM that understands Journaling FSs is not an acceptable compromize. (I had high hopes for lk2.4)
NT has NTFS. It is NOT a journaling FS, enough said.
All the other considerations aside..
The lack of desktop management tools comparable to NDS+Zenworks (on Linux) tips the scales in favour of Netware (for our environment).
3) eDirectory is the only multiplatform directory. Directories are not about savings, i.e. CFOs may not notice the saving but CIO will notice the ubiquity, get it?
Slashdot Mirror
Its called OIL.
The middleeast has it and there is a large untapped reserve in central asia (Iran, Afghanistan and southern russian republics).
GWB, like his father, is an oil man, if you know anything about the oil business its all about controlling the supply.
This is not a war on terrorism its a geo-economic chess game.
US foriegn policy has always been based on economics NOT democracy or freedom.
Please note the following..
BG = BattleStar Galactica
B5 = Babylon5
The original poster asked for BG not B5.
I'm too young or TOO OLD to remember BG very well so I don't recall the religous overtones.
closed source drivers, hopefully they will have a fix for that..
Just a minor correction..
i =1 484&p=4
NOT 128bit DDR memory:
nForce has two independent 64bit DDR memory buses, see..
http://www.anandtech.com/chipsets/showdoc.html?
When both banks are are populated (with a 64bit DDR DIMM in each) you have a "virtual" 128bit bus. However, if the two banks are interleaved, you do get 100% boost in bandwidth.
Note: more bandwidth is not what limits 1+GHz PCs, its memory latency and system contention.
nForce is the 1st chipset to attempt to address the issue of contention while NOT increasing memory latencies.
nForce does not use memory interleaving, it uses a memory crossbar.
memory interleaving:
Interleaving of different banks of memory which are in SERIES.
+ shortens address line setup time for sequential memory access.
+ upto 30% more bandwidth (depending on type of memory FPS/EDO/SDRAM) when the cache line is double (or quadruple) of the bus width.
memory crossbar = Interleaving of banks of memory which are in PARALLEL.
+ parallel memory transactions (if each is for a different bank).
+ improvements are less deterministic, depends on which transactions can be parallelized.
+ does reduce memory contention, i.e. different devices (CPU, Video, Disk, NIC) wanting access to memory at the same time.
For multimedia type applications (read games, DVD playback) this is a big help.
nForce's twin-bank memory sub-system reminds me of the Amiga's twin bank memory sub-system.
Great so you have localized storage of different versions and possibly localized loading of different versions.
.net becomes .not
"your binary has to ask for a particular, or minimum, version of the dll"
So with XP M$ will finally "try" (its not out yet) to fix their F**K UP versioning. How long before the majority of apps are "AWARE" of this "innovative feature"? (hint proper version control has been taught in software engineering for over 10 years).
Do you know why XP has to have this?
otherwise
Server has one version and the clients have other versions.
The Tutalin PIII is a redesign..l e/ 0,aid,42844,00.asp
k 7- 1.html
a) based on (www.tomshardware)'s article that a bigger brother will have 512KB of on-chip l2 cache (can't just stuff in more cache).
b) Intel minion's words..
http://www.pcworld.com/resource/printable/artic
From the processor design point of view dropping the microns does not automatically give you higher clock speeds. Your CPU has to be designed with enough stages to scale to higher clocks. A good reference for this point..
http://www.arstechnica.com/cpu/1q00/g4vsk7/g4vs
The copperMine 0.18 core was originally designed for 1.1GHz only (intel words, can't find a reference).
So will have a binary only kernel for the nForce?
If we are really good children (father know's best) nVidia may give us source for everything except the graphics card.
In either case, without good, open, graphics its not a open console spec.
Many peering agreements have clauses for charges based on usage differential, i.e..
How much of PSInet's bandwidth is used by C&W's traffic VERSUS how much of C&W's bandwidth is used by PSInet's traffic.
C&W can't expect to be paid for such charges so why continue to do business with PSInet?
Your head is stuck in the PCI specification manuals.
The reality is that *some* (possibly most) PCI devices..
a) from a hardware prespective don't like to share IRQ's
b) from a software prespective have crappy drivers that don't (for some devices can't) follow the specification close enough.
For any time critical application (video editing, server type stuff) shared IRQs can be a problem
With regards to i815 and 440BX..
i815 has a one way asynch. memory controller, i.e. supports a 133MHz front side bus processor with 100MHz PC100 memory.
440BX has a synch. memory controller.
What does this mean?
Synch. memory controllers can be made with fewer gates in series, i.e. the memory controller has less latency.
That account for most of the 0 to 5% difference in performance.
I have not looked into Novell stuff for about 6months, but I think you are mistaken..
e-directory (your name NDS) is NDS that can run on NetwareOS, WinNT/2K and Linux..
a) On WinNT/2K it actually replaces domain/AD as the authenticator.
b) on Linux it replaces the password file by using PAM modules to redirect authentications to NDS
What you are thinking of is DirXML a directory synchronizing daemon that maps parts of AD to NDS and vice-versa. IMO it is the slickest software from Novell since Netware 3.11 came out.
You create the mapping of NDS schema to/from AD and you can tell it what part of (container / organizational unit) your NDS maps to what part of AD. You are still running two directories which are being synchronized at an interval you decide. What makes it kick ass is the schema and attributes synch is all visual, point and click.
Dude are you a troll or an artist that didn't get a contract?
Even before the internet/napster, big labels were milking the public and the artists..
a) FCC busted a group of the big ones for CD price fixing.
b) most of the contracts offerred to no-name artists were just short of "sell your soul" and/or "sell your soul and we own your life as an artist for the duration of the contract"
Even before the internet became big, the music industry combined with distribution and marketing channels were being described as a racket. (Think AOL-TimeWarner, content + distribution).
Factor in the mainstream success of "manufactured bands" (BackStreetBoys, NewKidsOnTheBlock, etc) and you have to ask yourself, IS THERE ANY PLACE/MEDIUM FOR REAL ARTISTS?
We have 64bit, 66MHz PCI RIGHT NOW.h tm l
http://www.serverworks.com/frames/prodHE_frame.
Yes its Intel only, but the PCI 64bit, 66MHz specification exists.
AMD:
Hopefully, 760MP will have support for at least 64bit 33MHz. Not sure about 64bit, 66MHz.
So like the ad market is down, but ITS NOT EXTINCT.
They will probably have to go for a split (free/charge) model for different services..
Yahoo basic directory would be supported by ads.
Deluxe directory would be subsriber only.
This is my 1st post so bare with me..
Yes Novell is no longer NOS market leaders, when they were, NOS meant file and print services. Now NOS means a lot more. Does this mean Netware is dead? Perhaps Netware is dead/ing (I do not think so), but Novell!=Netware.
Multiplatform NDS is Novell and their recent products reflect this.
1) What I have observed about organizations with IT departments..
If the IT group responsible for server services does not have close ties to the IT group responsible for desktop services, you are more likely to run *nix (if the admin is smart and the manager has balls) otherwise M$.
IF this is not the case and the two groups have close ties or are one then suddenly netware+NDS+ZenWorks is a compelling solution for file and print services. Now with NDS on linux and Solaris it is possible to have one login+password for each user for ALL services.
2) I work in a "Netware Shop", we are not committed to Novell, (we only run Netware) email is unix, web is unix, Oracle is on unix. Each system is a separate userID+password. Yes we started with Netware 2.x to 3.x to 4.11. We are contemplating moving to nw5.x. For over a year I have been researching our upgrade options (for FILE SERVICES, to replace Netware 4.xx)
One of the key requirements is a Journaling File System.
NW5.x has NSS. A journaling filesystem which now has quota support (a requirement).
Linux has ReiserFS. It works great, but the lack of VMM that understands Journaling FSs is not an acceptable compromize. (I had high hopes for lk2.4)
NT has NTFS. It is NOT a journaling FS, enough said.
All the other considerations aside..
The lack of desktop management tools comparable to NDS+Zenworks (on Linux) tips the scales in favour of Netware (for our environment).
3) eDirectory is the only multiplatform directory. Directories are not about savings, i.e. CFOs may not notice the saving but CIO will notice the ubiquity, get it?