Re: IBM's Next Generation Mainframe Processor
>>> On Sat, Oct 13, 2007 at 5:26 PM, in message <[EMAIL PROTECTED]>, "Jim Elliott <[EMAIL PROTECTED]>" <[EMAIL PROTECTED]> wrote: -snip- > A few important things to note: > > 1) z6 is the name for the chip, not the name of the next > generation mainframe. > > 2) This is a presentation on the processor and SMB hub chips in > the next generation mainframe, not on the total package. Hence the subject of the email: mainframe processor. (I don't call the whole box a processor any more.) Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IBM's Next Generation Mainframe Processor
>>> On Sat, Oct 13, 2007 at 7:57 PM, in message <[EMAIL PROTECTED]>, John Summerfield <[EMAIL PROTECTED]> wrote: -snip- > PS Didn't know Americans know what km are. Most Americans do, it's just that very few of them are in the US. Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IBM's Next Generation Mainframe Processor
Jim Elliott <[EMAIL PROTECTED]> wrote: If you haven't already seen this, it's worth a look. It's a presentation by Charles Webb of IBM on the next IBM mainframe processor, the z6. (Don't ask me where "6" came from.) The thing that stood out for me was the 4GHz processor speed, but of course there's lots of other very good stuff as well. http://www2.hursley.ibm.com/decimal/IBM-z6-mainframe-microprocessor-Webb.pdf Mark: A few important things to note: 6 km wire. That's a farm-sized piece of wire (I had to stop to estimate the circumference of Dad's (former) farm. It would go around about once. PS Didn't know Americans know what km are. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IBM's Next Generation Mainframe Processor
> If you haven't already seen this, it's worth a look. It's a > presentation by Charles Webb of IBM on the next IBM mainframe > processor, the z6. (Don't ask me where "6" came from.) The > thing that stood out for me was the 4GHz processor speed, but > of course there's lots of other very good stuff as well. > http://www2.hursley.ibm.com/decimal/IBM-z6-mainframe-microprocessor-Webb.pdf Mark: A few important things to note: 1) z6 is the name for the chip, not the name of the next generation mainframe. 2) This is a presentation on the processor and SMB hub chips in the next generation mainframe, not on the total package. 3) The cycle time is 4GHz+ and just as with MIPS, GHz is a "meaningless indicator of processor speed". 4) This is an assumption on my part, but the z6 name be due to some parts of the chip being derived from Power 6 (e.g. the DFU). Jim -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: IBM's Next Generation Mainframe Processor
"We've turned the 9 upside down" - maybe that's the marketing plan :) Likely though that it is the Power6 family. Marcy Cortes "This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose, or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation." -Original Message- From: Linux on 390 Port [mailto:[EMAIL PROTECTED] On Behalf Of Mark Post Sent: Saturday, October 13, 2007 10:12 AM To: LINUX-390@VM.MARIST.EDU Subject: [LINUX-390] IBM's Next Generation Mainframe Processor If you haven't already seen this, it's worth a look. It's a presentation by Charles Webb of IBM on the next IBM mainframe processor, the z6. (Don't ask me where "6" came from.) The thing that stood out for me was the 4GHz processor speed, but of course there's lots of other very good stuff as well. http://www2.hursley.ibm.com/decimal/IBM-z6-mainframe-microprocessor-Webb.pdf Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 smime.p7s Description: S/MIME cryptographic signature
IBM's Next Generation Mainframe Processor
If you haven't already seen this, it's worth a look. It's a presentation by Charles Webb of IBM on the next IBM mainframe processor, the z6. (Don't ask me where "6" came from.) The thing that stood out for me was the 4GHz processor speed, but of course there's lots of other very good stuff as well. http://www2.hursley.ibm.com/decimal/IBM-z6-mainframe-microprocessor-Webb.pdf Mark Post -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: high water mark for swap space used?
Wouldn't it be reasonable and mostly trivial that 1) when a process is terminated, that any of it's pages that are on swap are issued a CP diagnose to discard the page? (requires a bit of Endicott work) 2) when a page is swapped in, make that page anonymous again, and issue that same diagnose? This eliminates duplicate resources of expensive storage. The result would be significantly less z/VM resources to maintain that swap disk. Rob van der Heij wrote: On 10/13/07, Carsten Otte <[EMAIL PROTECTED]> wrote: No method is in place to ever change a backing. Thus, a page will never be moved from one swap slot to a different swap slot. This is why linux is not very good at keeping swap usage local, and is not good at using low prio swap for hot pages. I don't think that were implied by what was suggested. It would even be a bad idea to move pages through swap (because you might cause them to page in just for re-ordering them). What would make a difference is the way slots are allocated on swap devices. As I mentioned between the lines of my posts, some of the apparent design criteria do not apply to VDISK (or even mainframe disk I/O in general). But that algorithm is probably in the generic part of Linux. The right way would probably be to add a way to steer the algorithm. In that case an option on swapon to select between first-fit and best-fit, for example. And while working on my pony, I would also like an API on the block device tell the driver to drop a block from backing store (also COW devices would enjoy that). Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 begin:vcard fn:Barton Robinson n:Robinson;Barton adr;dom:;;PO 390640;Mountain View;CA;94039-0640 email;internet:[EMAIL PROTECTED] title:Sr. Architect tel;work:650-964-8867 note:If you can't measure it, I'm just not interested x-mozilla-html:FALSE url:http://velocitysoftware.com version:2.1 end:vcard
Re: high water mark for swap space used?
On 10/13/07, Carsten Otte <[EMAIL PROTECTED]> wrote: > No method is in place to ever change a backing. Thus, a page will > never be moved from one swap slot to a different swap slot. This is > why linux is not very good at keeping swap usage local, and is not > good at using low prio swap for hot pages. I don't think that were implied by what was suggested. It would even be a bad idea to move pages through swap (because you might cause them to page in just for re-ordering them). What would make a difference is the way slots are allocated on swap devices. As I mentioned between the lines of my posts, some of the apparent design criteria do not apply to VDISK (or even mainframe disk I/O in general). But that algorithm is probably in the generic part of Linux. The right way would probably be to add a way to steer the algorithm. In that case an option on swapon to select between first-fit and best-fit, for example. And while working on my pony, I would also like an API on the block device tell the driver to drop a block from backing store (also COW devices would enjoy that). Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/ -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: SLES9 Installation - Very Basic
Froberg, David C wrote: If you have a lot of ISO images, you may need to increase the number of loop devices on the system. How do you increase the number of loop devices? modinfo loop Put the appropriate info in /etc/modprobe.conf or wherever. (why isn't that whereever?) -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
http://www-03.ibm.com/systems/z/os/linux/lcds/
Would this facility be appropriate for building CentOS5 (and maybe Fedora) for Zeds? There currently is no C5 for Zeds, and the likelihood of there being one doesn't seem too flash atm. -- Cheers John -- spambait [EMAIL PROTECTED] [EMAIL PROTECTED] Please do not reply off-list -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
Re: high water mark for swap space used?
Brandt, Mark H wrote: IMHO it would be more efficient to get IBM and Novel to address the issue and eliminate VDISK memory creep without having to configure multiple VDISKS with different priorities. That would fundamentally change the way linux memory management works today: Pages are distinguished in "anonymous" and "non anonymous" ones. Those that are non anonymous have a backing on disk, for example they belong to /bin/bash when running your command interpreter, or to a library. Anonymous ones usually come to life by malloc(). They don't have a backing on disk. When time comes that a page gets to the end of the inactive list, which means it is about to be discarded from main memory, we check if the page is anonymous or not. If is non anonymous (that is, page has a backing on disk) we write back the changes and discard it. For anonymous pages (no disk backing), they get a swap slot assigned from the lowest prio swap available and are considered non anonymous from here on: they're written back to their swap slot and discarded. When that page gets accessed again later, it is considered to be swap cache with a backing on disk: the swap slot. No method is in place to ever change a backing. Thus, a page will never be moved from one swap slot to a different swap slot. This is why linux is not very good at keeping swap usage local, and is not good at using low prio swap for hot pages. btw: I'd like to recommend Mel Gorman's book on this. Pdf is free on the internet. The title is "understanding the linux virtual memory manager". cheers, Carsten -- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
