I find it very handy in dev/stage environments where by definition, there are *lots* of unknowns.
Patrick Carroll | Enterprise Technical Architect L.L.Bean, Inc.(r) | Double L St. | Freeport ME 04033 http://www.llbean.com | pcarr...@llbean.com | 207.552.2426 CONFIDENTIALITY NOTICE: This e-mail and any attachments may contain confidential information that is legally privileged. The information is solely for the use of the intended recipient(s). Any disclosure, copying, distribution, or other use of this information is strictly prohibited. If you have received this e-mail in error, please notify the sender by return e-mail and delete this message. -----Original Message----- From: Linux on 390 Port [mailto:linux-...@vm.marist.edu] On Behalf Of Marcy Cortes Sent: Wednesday, July 29, 2009 7:33 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: Dasd_diag_mod question Question, what is the value of using diag for swapping to vdisk? Even if it is a more efficient driver, you're swapping to memory. How much does it save? And how much swapping would you need to be doing for any savings to be worthwhile? Wouldn't it be simpler to just increase the VM size to an amount that minimizes swapping? Or are there servers you *want* swapping a lot for some reason and if so why? Inquiring minds... Marcy "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:linux-...@vm.marist.edu] On Behalf Of Mark Post Sent: Wednesday, July 29, 2009 12:23 PM To: LINUX-390@VM.MARIST.EDU Subject: Re: [LINUX-390] Dasd_diag_mod question >>> On 7/29/2009 at 3:09 PM, "Mrohs, Ray" <ray.mr...@usdoj.gov> wrote: -snip- > Is this the expected behavior, or should mkinitrd/zipl have made it > all transparent? > I do see the DIAG DASDS during the mkinitrd process. No, I would have expected it to be transparent. Email me your new initrd off list and I'll take a look at it. I'm suspecting that for whatever reason, dasd_diag_mod isn't being included in it. If that's the case, adding it to /etc/sysconfig/kernels will fix it, but I'd like to see the initrd. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
