From keepeffort at naver.com Mon Oct 1 04:27:00 2007 From: keepeffort at naver.com (=?US-ASCII?B?a2VlcGVmZm9ydA==?=) Date: Mon, 01 Oct 2007 17:27:00 +0900 Subject: [Disksim-users] DiskSim API Message-ID: Hi all, I'm going to test 'mydisk.c'. However, I didn't find the DiskSim API. Where is DiskSim API? And how to use it? Thanks, YG -------------- next part -------------- An HTML attachment was scrubbed... URL: From zgy04 at 126.com Mon Oct 1 05:02:57 2007 From: zgy04 at 126.com (Steve) Date: Mon, 1 Oct 2007 17:02:57 +0800 Subject: [Disksim-users] DiskSim API References: Message-ID: <200710011702559270741@126.com> First, you maybe want to read the manual from http://www.pdl.cmu.edu/DiskSim/ ?? ======== 2007-10-01 16:51:22 ???????? ======== Hi all, I'm going to test 'mydisk.c'. However, I didn't find the DiskSim API. Where is DiskSim API? And how to use it? Thanks, YG = = = = = = = = = = = = = = = = = = = = = = ????????? ?? ??????????????Steve ??????????????zgy04 at 126.com ???????????????2007-10-01 -------------- next part -------------- An HTML attachment was scrubbed... URL: From alandd at consultpros.com Fri Oct 5 22:29:50 2007 From: alandd at consultpros.com (Alan Dayley) Date: Fri, 05 Oct 2007 19:29:50 -0700 Subject: [Disksim-users] Make errors. Old compiler required? Message-ID: <4706F31E.4090907@consultpros.com> I am attempting my first compile of disksim 3.0. It fails with plenty of warnings and errors. I found an email in the archive from more than a year ago that states gcc 2.95 should be used to compile. 1. Is there a build "howto" or some other build guide? 2. Is an old version of gcc still required? 3. Is there an effort to bring the code base forward to current tools? BTW, I am attempting to build on an OpenSUSE Linux 10.2 installation using gcc 4.1.2. Thanks. Alan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 249 bytes Desc: OpenPGP digital signature URL: From alandd at consultpros.com Fri Oct 5 22:54:10 2007 From: alandd at consultpros.com (Alan Dayley) Date: Fri, 05 Oct 2007 19:54:10 -0700 Subject: [Disksim-users] Make errors. Old compiler required? In-Reply-To: <4706F31E.4090907@consultpros.com> References: <4706F31E.4090907@consultpros.com> Message-ID: <4706F8D2.6020405@consultpros.com> Alan Dayley wrote: > I am attempting my first compile of disksim 3.0. It fails with plenty > of warnings and errors. I found an email in the archive from more than > a year ago that states gcc 2.95 should be used to compile. > > 1. Is there a build "howto" or some other build guide? > > 2. Is an old version of gcc still required? > > 3. Is there an effort to bring the code base forward to current tools? > > BTW, I am attempting to build on an OpenSUSE Linux 10.2 installation > using gcc 4.1.2. (Answering myself...) I did more digging in the email archive and found this message: https://sos.ece.cmu.edu/pipermail/disksim-users/2007-August/000204.html with an attached patch file. After application the build was successful, albeit with plenty of warnings. The "runvalid" test was successful too. Perhaps this message should be referenced on the home page until the patch is properly integrated? Alan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 249 bytes Desc: OpenPGP digital signature URL: From kamashay at yahoo.com Sat Oct 6 08:40:45 2007 From: kamashay at yahoo.com (shay raz) Date: Sat, 6 Oct 2007 05:40:45 -0700 (PDT) Subject: [Disksim-users] Make errors. Old compiler required? In-Reply-To: <4706F8D2.6020405@consultpros.com> Message-ID: <739414.91968.qm@web51310.mail.re2.yahoo.com> Dear Alan, compiling DiskSim is a known issue. please see the following good instructions-email: https://sos.ece.cmu.edu/pipermail/disksim-users/2006-November/000096.html if you are able to compile the code under a different platform, please share the how-to knowledge with the rest of the community. Best, Shay Alan Dayley wrote: Alan Dayley wrote: > I am attempting my first compile of disksim 3.0. It fails with plenty > of warnings and errors. I found an email in the archive from more than > a year ago that states gcc 2.95 should be used to compile. > > 1. Is there a build "howto" or some other build guide? > > 2. Is an old version of gcc still required? > > 3. Is there an effort to bring the code base forward to current tools? > > BTW, I am attempting to build on an OpenSUSE Linux 10.2 installation > using gcc 4.1.2. (Answering myself...) I did more digging in the email archive and found this message: https://sos.ece.cmu.edu/pipermail/disksim-users/2007-August/000204.html with an attached patch file. After application the build was successful, albeit with plenty of warnings. The "runvalid" test was successful too. Perhaps this message should be referenced on the home page until the patch is properly integrated? Alan _______________________________________________ Disksim-users mailing list Disksim-users at ece.cmu.edu https://sos.ece.cmu.edu/mailman/listinfo/disksim-users --------------------------------- Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. -------------- next part -------------- An HTML attachment was scrubbed... URL: From alandd at consultpros.com Sat Oct 6 12:14:57 2007 From: alandd at consultpros.com (Alan Dayley) Date: Sat, 06 Oct 2007 09:14:57 -0700 Subject: [Disksim-users] Make errors. Old compiler required? In-Reply-To: <739414.91968.qm@web51310.mail.re2.yahoo.com> References: <739414.91968.qm@web51310.mail.re2.yahoo.com> Message-ID: <4707B481.6050208@consultpros.com> Thanks, Shay. For clarity in the archive... As documented in my reply to myself, the referenced patch allowed me to compile and execute a successful "runvalid" on my platform: OpenSUSE 10.2, GCC 4.1.2 Alan shay raz wrote: > Dear Alan, > > compiling DiskSim is a known issue. > please see the following good instructions-email: > https://sos.ece.cmu.edu/pipermail/disksim-users/2006-November/000096.html > if you are able to compile the code under a different platform, please share > the how-to knowledge with the rest of the community. > > Best, > Shay > > */Alan Dayley /* wrote: > > Alan Dayley wrote: > > I am attempting my first compile of disksim 3.0. It fails with plenty > > of warnings and errors. I found an email in the archive from more than > > a year ago that states gcc 2.95 should be used to compile. > > > > 1. Is there a build "howto" or some other build guide? > > > > 2. Is an old version of gcc still required? > > > > 3. Is there an effort to bring the code base forward to current tools? > > > > BTW, I am attempting to build on an OpenSUSE Linux 10.2 installation > > using gcc 4.1.2. > > (Answering myself...) > > I did more digging in the email archive and found this message: > > https://sos.ece.cmu.edu/pipermail/disksim-users/2007-August/000204.html > > with an attached patch file. After application the build was > successful, albeit with plenty of warnings. The "runvalid" test was > successful too. > > Perhaps this message should be referenced on the home page until the > patch is properly integrated? > > Alan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 249 bytes Desc: OpenPGP digital signature URL: From alandd at consultpros.com Sat Oct 6 12:27:11 2007 From: alandd at consultpros.com (Alan Dayley) Date: Sat, 06 Oct 2007 09:27:11 -0700 Subject: [Disksim-users] Bring code forward to current compiler? Message-ID: <4707B75F.7070203@consultpros.com> Asking Disksim users to step back to the 2.95 version of GCC is a bit odd, in my opinion. Being new to the program I know little of it's history. Perhaps someone can fill me in on the situation. 1. Is there a technical reason or difficulty that has prevent the port forward? 2. Is there a known requirement to stay back on the older compiler? 3. What is the patch submission method if one were to solve this issue? Alan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 249 bytes Desc: OpenPGP digital signature URL: From lmq06 at mails.tsinghua.edu.cn Mon Oct 8 05:21:49 2007 From: lmq06 at mails.tsinghua.edu.cn (lmq06) Date: Mon, 8 Oct 2007 17:21:49 +0800 Subject: [Disksim-users] What does PARITY_TABLE mean in disksim3.0 ? Message-ID: <200710081721492503391@mails.tsinghua.edu.cn> Hi, When I use disksim 3.0, I find that there is a redendancy scheme, named PARITY_TABLE, which is not introduced in the maual. What does PARITY_TABLE mean? Thank you very much! Mingqiang Li 2007-10-08 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mingqiang LI.vcf Type: text/x-vcard Size: 141 bytes Desc: not available URL: From michael.meeks at novell.com Mon Oct 8 08:48:19 2007 From: michael.meeks at novell.com (Michael Meeks) Date: Mon, 08 Oct 2007 13:48:19 +0100 Subject: [Disksim-users] Bring code forward to current compiler? In-Reply-To: <4707B75F.7070203@consultpros.com> References: <4707B75F.7070203@consultpros.com> Message-ID: <1191847699.12463.71.camel@localhost> Hi Alan, On Sat, 2007-10-06 at 09:27 -0700, Alan Dayley wrote: > Asking Disksim users to step back to the 2.95 version of GCC is a bit > odd, in my opinion. Being new to the program I know little of it's > history. Perhaps someone can fill me in on the situation. :-) DiskSim is unmaintained (unfortunately). > 1. Is there a technical reason or difficulty that has prevent the port > forward? Nope; nothing I'm aware of. If you go to http://live.gnome.org/iogrind and look at 'getting the code' - you can download a version of disksim-3.0 embedded into iogrind with a number of bug fixes, autoconf-isation, that will build ~without warnings on a recent SUSE. Do feel free to rip it out of there for your own use :-) HTH, Michael. -- michael.meeks at novell.com <><, Pseudo Engineer, itinerant idiot From ganger at ece.cmu.edu Mon Oct 8 17:22:18 2007 From: ganger at ece.cmu.edu (Greg Ganger) Date: Mon, 8 Oct 2007 17:22:18 -0400 (EDT) Subject: [Disksim-users] What does PARITY_TABLE mean in disksim3.0 ? In-Reply-To: <200710081721492503391@mails.tsinghua.edu.cn> References: <200710081721492503391@mails.tsinghua.edu.cn> Message-ID: If memory serves, that is an internal type used to represent certain of the specifiable redundancy scheme types (those that have non-trivial repeating patterns). Greg On Mon, 8 Oct 2007, lmq06 wrote: > Hi, > When I use disksim 3.0, I find that there is a redendancy scheme, named PARITY_TABLE, which is not introduced in the maual. What does PARITY_TABLE mean? Thank you very much! > > Mingqiang Li > > > > > 2007-10-08 > From lmq06 at mails.tsinghua.edu.cn Tue Oct 9 01:43:09 2007 From: lmq06 at mails.tsinghua.edu.cn (lmq06) Date: Tue, 9 Oct 2007 13:43:09 +0800 Subject: [Disksim-users] What does PARITY_TABLE mean in disksim3.0 ? References: <200710081721492503391@mails.tsinghua.edu.cn>, Message-ID: <200710091343093752184@mails.tsinghua.edu.cn> Thank you very much! Mingqiang 2007-10-09 ???? Greg Ganger ????? 2007-10-09 05:22:21 ???? lmq06 ??? disksim-users; Greg Ganger ??? Re: [Disksim-users] What does PARITY_TABLE mean in disksim3.0 ? If memory serves, that is an internal type used to represent certain of the specifiable redundancy scheme types (those that have non-trivial repeating patterns). Greg On Mon, 8 Oct 2007, lmq06 wrote: > Hi, > When I use disksim 3.0, I find that there is a redendancy scheme, named PARITY_TABLE, which is not introduced in the maual. What does PARITY_TABLE mean? Thank you very much! > > Mingqiang Li > > > > > 2007-10-08 > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mingqiang LI.vcf Type: text/x-vcard Size: 141 bytes Desc: not available URL: From lmq06 at mails.tsinghua.edu.cn Tue Oct 9 05:09:08 2007 From: lmq06 at mails.tsinghua.edu.cn (lmq06) Date: Tue, 9 Oct 2007 17:09:08 +0800 Subject: [Disksim-users] Which functions in source codes simulate the small write operation for RAID in Disksim 3.0? Message-ID: <200710091709083751507@mails.tsinghua.edu.cn> Hi, Now I am doing a simulation experiment, and need to modify the source codes of small write operation for RAID in Disksim 3.0. But which functions in the source codes simulate the operation? And how these functions implement the simulation? Thank you very much! Mingqiang Li 2007-10-09 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mingqiang LI.vcf Type: text/x-vcard Size: 141 bytes Desc: not available URL: From ganger at ece.cmu.edu Tue Oct 9 11:55:19 2007 From: ganger at ece.cmu.edu (Greg Ganger) Date: Tue, 9 Oct 2007 11:55:19 -0400 (EDT) Subject: [Disksim-users] Which functions in source codes simulate the small write operation for RAID in Disksim 3.0? In-Reply-To: <200710091709083751507@mails.tsinghua.edu.cn> References: <200710091709083751507@mails.tsinghua.edu.cn> Message-ID: hmm, should be pretty obvious in following the types (like PARITY_TABLE) that you've already found in the code. The array activities start in disksim_logorg.c. Good luck! Greg On Tue, 9 Oct 2007, lmq06 wrote: > Hi, > Now I am doing a simulation experiment, and need to modify the source codes of small write operation for RAID in Disksim 3.0. But which functions in the source codes simulate the operation? And how these functions implement the simulation? Thank you very much! > > > > Mingqiang Li > > > > 2007-10-09 > From lmq06 at mails.tsinghua.edu.cn Wed Oct 10 01:27:13 2007 From: lmq06 at mails.tsinghua.edu.cn (lmq06) Date: Wed, 10 Oct 2007 13:27:13 +0800 Subject: [Disksim-users] Which functions in source codes simulate the small write operation for RAID in Disksim 3.0? References: <200710091709083751507@mails.tsinghua.edu.cn>, Message-ID: <200710101327134218960@mails.tsinghua.edu.cn> Thank you for your help Mingqiang Li 2007-10-10 ???? Greg Ganger ????? 2007-10-09 23:55:25 ???? lmq06 ??? disksim-users; Greg Ganger ??? Re: [Disksim-users] Which functions in source codes simulate thesmall write operation for RAID in Disksim 3.0? hmm, should be pretty obvious in following the types (like PARITY_TABLE) that you've already found in the code. The array activities start in disksim_logorg.c. Good luck! Greg On Tue, 9 Oct 2007, lmq06 wrote: > Hi, > Now I am doing a simulation experiment, and need to modify the source codes of small write operation for RAID in Disksim 3.0. But which functions in the source codes simulate the operation? And how these functions implement the simulation? Thank you very much! > > > > Mingqiang Li > > > > 2007-10-09 > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 14.gif Type: image/gif Size: 1662 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mingqiang LI.vcf Type: text/x-vcard Size: 141 bytes Desc: not available URL: From lmq06 at mails.tsinghua.edu.cn Mon Oct 15 08:43:57 2007 From: lmq06 at mails.tsinghua.edu.cn (lmq06) Date: Mon, 15 Oct 2007 20:43:57 +0800 Subject: [Disksim-users] What does the event type CHECKPOINT mean in Disksim 3.0? Message-ID: <200710152043570620238@mails.tsinghua.edu.cn> Hi, What does the event type CHECKPOINT mean in Disksim 3.0? Thank you very much Mingqiang Li 2007-10-15 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 14.gif Type: image/gif Size: 1662 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mingqiang LI.vcf Type: text/x-vcard Size: 141 bytes Desc: not available URL: From ganger at ece.cmu.edu Wed Oct 17 19:52:54 2007 From: ganger at ece.cmu.edu (Greg Ganger) Date: Wed, 17 Oct 2007 19:52:54 -0400 (EDT) Subject: [Disksim-users] What does the event type CHECKPOINT mean in Disksim 3.0? In-Reply-To: <200710152043570620238@mails.tsinghua.edu.cn> References: <200710152043570620238@mails.tsinghua.edu.cn> Message-ID: It relates to checkpointing functionality in DiskSim. I would not suggest relying on it. Greg On Mon, 15 Oct 2007, lmq06 wrote: > Hi, > What does the event type CHECKPOINT mean in Disksim 3.0? > Thank you very much > > > Mingqiang Li > > > > 2007-10-15 > From lmq06 at mails.tsinghua.edu.cn Thu Oct 18 12:15:50 2007 From: lmq06 at mails.tsinghua.edu.cn (lmq06) Date: Fri, 19 Oct 2007 00:15:50 +0800 Subject: [Disksim-users] Why does controller_bus_ownership_grant problem happen? Message-ID: <200710190015500873939@mails.tsinghua.edu.cn> Hi, When I run disksim3.0, I encounter a problem as follows: ----------------------------------------------------------------------------------------------------- Assertion failed: simtime = 8.643000 totalreqs = 1 disksim: disksim_controller.c:299: controller_bus_ownership_grant: Assertion `tmp != ((void *)0)' failed. Aborted ----------------------------------------------------------------------------------------------------- Why does this problem happen? Thank you Mingqiang Li The system topology is as follows: ----------------------------------------------------------------------------------------------------- # system topology topology disksim_iodriver driver0 [ disksim_bus outerbus [ disksim_ctlr ctlr0 [ disksim_bus bus0 [ disksim_disk disk0 [] ] # end of bus0 ], # end of ctlr0 disksim_ctlr ctlr1 [ disksim_bus bus1 [ disksim_disk disk1 [] ] # end of bus1 ], # end of ctlr1 disksim_ctlr ctlr2 [ disksim_bus bus2 [ disksim_disk disk2 [] ] # end of bus2 ], # end of ctlr2 disksim_ctlr ctlr3 [ disksim_bus bus3 [ disksim_disk disk3 [] ] # end of bus3 ], # end of ctlr3 disksim_ctlr ctlr4 [ disksim_bus bus4 [ disksim_disk disk4 [] ] # end of bus4 ], # end of ctlr4 disksim_ctlr ctlr5 [ disksim_bus bus5 [ disksim_disk disk5 [] ] # end of bus5 ], # end of ctlr5 disksim_ctlr ctlr6 [ disksim_bus bus6 [ disksim_disk disk6 [] ] # end of bus6 ], # end of ctlr6 disksim_ctlr ctlr7 [ disksim_bus bus7 [ disksim_disk disk7 [] ] # end of bus7 ], # end of ctlr7 disksim_ctlr ctlr8 [ disksim_bus bus8 [ disksim_disk disk8 [] ] # end of bus8 ], # end of ctlr8 disksim_ctlr ctlr9 [ disksim_bus bus9 [ disksim_disk disk9 [] ] # end of bus9 ], # end of ctlr9 disksim_ctlr ctlr10 [ disksim_bus bus10 [ disksim_disk disk10 [] ] # end of bus10 ], # end of ctlr10 disksim_ctlr ctlr11 [ disksim_bus bus11 [ disksim_disk disk11 [] ] # end of bus11 ],# end of ctlr11 disksim_ctlr ctlr12 [ disksim_bus bus12 [ disksim_disk disk12 [] ] # end of bus12 ], # end of ctlr12 disksim_ctlr ctlr13 [ disksim_bus bus13 [ disksim_disk disk13 [] ] # end of bus13 ], # end of ctlr13 disksim_ctlr ctlr14 [ disksim_bus bus14 [ disksim_disk disk14 [] ] # end of bus14 ], # end of ctlr14 disksim_ctlr ctlr15 [ disksim_bus bus15 [ disksim_disk disk15 [] ] # end of bus15 ], # end of ctlr15 disksim_ctlr ctlr16 [ disksim_bus bus16 [ disksim_disk disk16 [] ] # end of bus16 ], # end of ctlr16 disksim_ctlr ctlr17 [ disksim_bus bus17 [ disksim_disk disk17 [] ] # end of bus17 ], # end of ctlr17 disksim_ctlr ctlr18 [ disksim_bus bus18 [ disksim_disk disk18 [] ] # end of bus18 ], # end of ctlr18 disksim_ctlr ctlr19 [ disksim_bus bus19 [ disksim_disk disk19 [] ] # end of bus19 ], # end of ctlr19 disksim_ctlr ctlr20 [ disksim_bus bus20 [ disksim_disk disk20 [] ] # end of bus20 ] # end of ctlr20 ] # end of outerbus ] # end of driver0 # end of system topology ----------------------------------------------------------------------------------------------------- 2007-10-19 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 14.gif Type: image/gif Size: 1662 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mingqiang LI.vcf Type: text/x-vcard Size: 141 bytes Desc: not available URL: From bucy at gloop.org Thu Oct 18 20:35:26 2007 From: bucy at gloop.org (John Bucy) Date: Thu, 18 Oct 2007 17:35:26 -0700 Subject: [Disksim-users] Why does controller_bus_ownership_grant problem happen? In-Reply-To: <200710190015500873939@mails.tsinghua.edu.cn> References: <200710190015500873939@mails.tsinghua.edu.cn> Message-ID: <4fc1e0430710181735v7a5a0c17y32dd034e1e34610b@mail.gmail.com> Hmm ... that assert is new to me. There may be some static limitations on the number of devices per bus, etc -- I've never been very familiar with that part of the code. Please write back when you figure it out so we know :) john On Oct 18, 2007 9:15 AM, lmq06 wrote: > > > Hi, > When I run disksim3.0, I encounter a problem as follows: > ----------------------------------------------------------------------------------------------------- > Assertion failed: > simtime = 8.643000 > totalreqs = 1 > disksim: disksim_controller.c:299: controller_bus_ownership_grant: > Assertion `tmp != ((void *)0)' failed. > Aborted > > ----------------------------------------------------------------------------------------------------- > Why does this problem happen? Thank you > > > > Mingqiang Li > > > The system topology is as follows: > > ----------------------------------------------------------------------------------------------------- > > > # system topology > > topology disksim_iodriver driver0 [ > > disksim_bus outerbus [ > > disksim_ctlr ctlr0 [ > > disksim_bus bus0 [ > > disksim_disk disk0 [] > > ] # end of bus0 > > ], # end of ctlr0 > > > > disksim_ctlr ctlr1 [ > > disksim_bus bus1 [ > > disksim_disk disk1 [] > > ] # end of bus1 > > ], # end of ctlr1 > > > > disksim_ctlr ctlr2 [ > > disksim_bus bus2 [ > > disksim_disk disk2 [] > > ] # end of bus2 > > ], # end of ctlr2 > > > > disksim_ctlr ctlr3 [ > > disksim_bus bus3 [ > > disksim_disk disk3 [] > > ] # end of bus3 > > ], # end of ctlr3 > > > > disksim_ctlr ctlr4 [ > > disksim_bus bus4 [ > > disksim_disk disk4 [] > > ] # end of bus4 > > ], # end of ctlr4 > > > > disksim_ctlr ctlr5 [ > > disksim_bus bus5 [ > > disksim_disk disk5 [] > > ] # end of bus5 > > ], # end of ctlr5 > > > > disksim_ctlr ctlr6 [ > > disksim_bus bus6 [ > > disksim_disk disk6 [] > > ] # end of bus6 > > ], # end of ctlr6 > > > > disksim_ctlr ctlr7 [ > > disksim_bus bus7 [ > > disksim_disk disk7 [] > > ] # end of bus7 > > ], # end of ctlr7 > > > > disksim_ctlr ctlr8 [ > > disksim_bus bus8 [ > > disksim_disk disk8 [] > > ] # end of bus8 > > ], # end of ctlr8 > > > > disksim_ctlr ctlr9 [ > > disksim_bus bus9 [ > > disksim_disk disk9 [] > > ] # end of bus9 > > ], # end of ctlr9 > > > > disksim_ctlr ctlr10 [ > > disksim_bus bus10 [ > > disksim_disk disk10 [] > > ] # end of bus10 > > ], # end of ctlr10 > > > > disksim_ctlr ctlr11 [ > > disksim_bus bus11 [ > > disksim_disk disk11 [] > > ] # end of bus11 > > ],# end of ctlr11 > > > > disksim_ctlr ctlr12 [ > > disksim_bus bus12 [ > > disksim_disk disk12 [] > > ] # end of bus12 > > ], # end of ctlr12 > > > > disksim_ctlr ctlr13 [ > > disksim_bus bus13 [ > > disksim_disk disk13 [] > > ] # end of bus13 > > ], # end of ctlr13 > > > > disksim_ctlr ctlr14 [ > > disksim_bus bus14 [ > > disksim_disk disk14 [] > > ] # end of bus14 > > ], # end of ctlr14 > > > > disksim_ctlr ctlr15 [ > > disksim_bus bus15 [ > > disksim_disk disk15 [] > > ] # end of bus15 > > ], # end of ctlr15 > > > > disksim_ctlr ctlr16 [ > > disksim_bus bus16 [ > > disksim_disk disk16 [] > > ] # end of bus16 > > ], # end of ctlr16 > > > > disksim_ctlr ctlr17 [ > > disksim_bus bus17 [ > > disksim_disk disk17 [] > > ] # end of bus17 > > ], # end of ctlr17 > > > > disksim_ctlr ctlr18 [ > > disksim_bus bus18 [ > > disksim_disk disk18 [] > > ] # end of bus18 > > ], # end of ctlr18 > > > > disksim_ctlr ctlr19 [ > > disksim_bus bus19 [ > > disksim_disk disk19 [] > > ] # end of bus19 > > ], # end of ctlr19 > > > > disksim_ctlr ctlr20 [ > > disksim_bus bus20 [ > > disksim_disk disk20 [] > > ] # end of bus20 > > ] # end of ctlr20 > > > > ] # end of outerbus > > ] # end of driver0 > > # end of system topology > ----------------------------------------------------------------------------------------------------- > > ________________________________ > > 2007-10-19 > _______________________________________________ > Disksim-users mailing list > Disksim-users at ece.cmu.edu > https://sos.ece.cmu.edu/mailman/listinfo/disksim-users > > From ll2 at rice.edu Thu Oct 18 21:02:00 2007 From: ll2 at rice.edu (ll2 at rice.edu) Date: Thu, 18 Oct 2007 20:02:00 -0500 Subject: [Disksim-users] Why does controller_bus_ownership_grant problem happen? In-Reply-To: <4fc1e0430710181735v7a5a0c17y32dd034e1e34610b@mail.gmail.com> References: <200710190015500873939@mails.tsinghua.edu.cn> <4fc1e0430710181735v7a5a0c17y32dd034e1e34610b@mail.gmail.com> Message-ID: <1192755720.47180208d3c10@webmail.mail.rice.edu> Hi, In the manual of DiskSim, there is limitation of device per bus: "A bus can have no more than 15 disks or controllers attached to it.". In this case, there are 20 disks per bus. One alternative is that partitioning the disks into several groups, then connect them. Lanyue Lu Quoting John Bucy : > Hmm ... that assert is new to me. There may be some static > limitations on the number of devices per bus, etc -- I've never been > very familiar with that part of the code. Please write back when you > figure it out so we know :) > > > > john > > On Oct 18, 2007 9:15 AM, lmq06 wrote: > > > > > > Hi, > > When I run disksim3.0, I encounter a problem as follows: > > > ----------------------------------------------------------------------------------------------------- > > Assertion failed: > > simtime = 8.643000 > > totalreqs = 1 > > disksim: disksim_controller.c:299: controller_bus_ownership_grant: > > Assertion `tmp != ((void *)0)' failed. > > Aborted > > > > > ----------------------------------------------------------------------------------------------------- > > Why does this problem happen? Thank you > > > > > > > > Mingqiang Li > > > > > > The system topology is as follows: > > > > > ----------------------------------------------------------------------------------------------------- > > > > > > # system topology > > > > topology disksim_iodriver driver0 [ > > > > disksim_bus outerbus [ > > > > disksim_ctlr ctlr0 [ > > > > disksim_bus bus0 [ > > > > disksim_disk disk0 [] > > > > ] # end of bus0 > > > > ], # end of ctlr0 > > > > > > > > disksim_ctlr ctlr1 [ > > > > disksim_bus bus1 [ > > > > disksim_disk disk1 [] > > > > ] # end of bus1 > > > > ], # end of ctlr1 > > > > > > > > disksim_ctlr ctlr2 [ > > > > disksim_bus bus2 [ > > > > disksim_disk disk2 [] > > > > ] # end of bus2 > > > > ], # end of ctlr2 > > > > > > > > disksim_ctlr ctlr3 [ > > > > disksim_bus bus3 [ > > > > disksim_disk disk3 [] > > > > ] # end of bus3 > > > > ], # end of ctlr3 > > > > > > > > disksim_ctlr ctlr4 [ > > > > disksim_bus bus4 [ > > > > disksim_disk disk4 [] > > > > ] # end of bus4 > > > > ], # end of ctlr4 > > > > > > > > disksim_ctlr ctlr5 [ > > > > disksim_bus bus5 [ > > > > disksim_disk disk5 [] > > > > ] # end of bus5 > > > > ], # end of ctlr5 > > > > > > > > disksim_ctlr ctlr6 [ > > > > disksim_bus bus6 [ > > > > disksim_disk disk6 [] > > > > ] # end of bus6 > > > > ], # end of ctlr6 > > > > > > > > disksim_ctlr ctlr7 [ > > > > disksim_bus bus7 [ > > > > disksim_disk disk7 [] > > > > ] # end of bus7 > > > > ], # end of ctlr7 > > > > > > > > disksim_ctlr ctlr8 [ > > > > disksim_bus bus8 [ > > > > disksim_disk disk8 [] > > > > ] # end of bus8 > > > > ], # end of ctlr8 > > > > > > > > disksim_ctlr ctlr9 [ > > > > disksim_bus bus9 [ > > > > disksim_disk disk9 [] > > > > ] # end of bus9 > > > > ], # end of ctlr9 > > > > > > > > disksim_ctlr ctlr10 [ > > > > disksim_bus bus10 [ > > > > disksim_disk disk10 [] > > > > ] # end of bus10 > > > > ], # end of ctlr10 > > > > > > > > disksim_ctlr ctlr11 [ > > > > disksim_bus bus11 [ > > > > disksim_disk disk11 [] > > > > ] # end of bus11 > > > > ],# end of ctlr11 > > > > > > > > disksim_ctlr ctlr12 [ > > > > disksim_bus bus12 [ > > > > disksim_disk disk12 [] > > > > ] # end of bus12 > > > > ], # end of ctlr12 > > > > > > > > disksim_ctlr ctlr13 [ > > > > disksim_bus bus13 [ > > > > disksim_disk disk13 [] > > > > ] # end of bus13 > > > > ], # end of ctlr13 > > > > > > > > disksim_ctlr ctlr14 [ > > > > disksim_bus bus14 [ > > > > disksim_disk disk14 [] > > > > ] # end of bus14 > > > > ], # end of ctlr14 > > > > > > > > disksim_ctlr ctlr15 [ > > > > disksim_bus bus15 [ > > > > disksim_disk disk15 [] > > > > ] # end of bus15 > > > > ], # end of ctlr15 > > > > > > > > disksim_ctlr ctlr16 [ > > > > disksim_bus bus16 [ > > > > disksim_disk disk16 [] > > > > ] # end of bus16 > > > > ], # end of ctlr16 > > > > > > > > disksim_ctlr ctlr17 [ > > > > disksim_bus bus17 [ > > > > disksim_disk disk17 [] > > > > ] # end of bus17 > > > > ], # end of ctlr17 > > > > > > > > disksim_ctlr ctlr18 [ > > > > disksim_bus bus18 [ > > > > disksim_disk disk18 [] > > > > ] # end of bus18 > > > > ], # end of ctlr18 > > > > > > > > disksim_ctlr ctlr19 [ > > > > disksim_bus bus19 [ > > > > disksim_disk disk19 [] > > > > ] # end of bus19 > > > > ], # end of ctlr19 > > > > > > > > disksim_ctlr ctlr20 [ > > > > disksim_bus bus20 [ > > > > disksim_disk disk20 [] > > > > ] # end of bus20 > > > > ] # end of ctlr20 > > > > > > > > ] # end of outerbus > > > > ] # end of driver0 > > > > # end of system topology > > > ----------------------------------------------------------------------------------------------------- > > > > ________________________________ > > > > 2007-10-19 > > _______________________________________________ > > Disksim-users mailing list > > Disksim-users at ece.cmu.edu > > https://sos.ece.cmu.edu/mailman/listinfo/disksim-users > > > > > _______________________________________________ > Disksim-users mailing list > Disksim-users at ece.cmu.edu > https://sos.ece.cmu.edu/mailman/listinfo/disksim-users > > From lmq06 at mails.tsinghua.edu.cn Fri Oct 19 01:18:35 2007 From: lmq06 at mails.tsinghua.edu.cn (lmq06) Date: Fri, 19 Oct 2007 13:18:35 +0800 Subject: [Disksim-users] Why does controller_bus_ownership_grant problem happen? References: <200710190015500873939@mails.tsinghua.edu.cn>, <4fc1e0430710181735v7a5a0c17y32dd034e1e34610b@mail.gmail.com>, <1192755720.47180208d3c10@webmail.mail.rice.edu> Message-ID: <200710191318348900932@mails.tsinghua.edu.cn> Thank you very much Mingqiang Li 2007-10-19 ???? ll2 at rice.edu ????? 2007-10-19 09:02:04 ???? disksim-users at ece.cmu.edu ??? lmq06 at mails.tsinghua.edu.cn; bucy at gloop.org ??? Re: [Disksim-users] Why does controller_bus_ownership_grant problem happen? Hi, In the manual of DiskSim, there is limitation of device per bus: "A bus can have no more than 15 disks or controllers attached to it.". In this case, there are 20 disks per bus. One alternative is that partitioning the disks into several groups, then connect them. Lanyue Lu Quoting John Bucy : > Hmm ... that assert is new to me. There may be some static > limitations on the number of devices per bus, etc -- I've never been > very familiar with that part of the code. Please write back when you > figure it out so we know :) > > > > john > > On Oct 18, 2007 9:15 AM, lmq06 wrote: > > > > > > Hi, > > When I run disksim3.0, I encounter a problem as follows: > > > ----------------------------------------------------------------------------------------------------- > > Assertion failed: > > simtime = 8.643000 > > totalreqs = 1 > > disksim: disksim_controller.c:299: controller_bus_ownership_grant: > > Assertion `tmp != ((void *)0)' failed. > > Aborted > > > > > ----------------------------------------------------------------------------------------------------- > > Why does this problem happen? Thank you > > > > > > > > Mingqiang Li > > > > > > The system topology is as follows: > > > > > ----------------------------------------------------------------------------------------------------- > > > > > > # system topology > > > > topology disksim_iodriver driver0 [ > > > > disksim_bus outerbus [ > > > > disksim_ctlr ctlr0 [ > > > > disksim_bus bus0 [ > > > > disksim_disk disk0 [] > > > > ] # end of bus0 > > > > ], # end of ctlr0 > > > > > > > > disksim_ctlr ctlr1 [ > > > > disksim_bus bus1 [ > > > > disksim_disk disk1 [] > > > > ] # end of bus1 > > > > ], # end of ctlr1 > > > > > > > > disksim_ctlr ctlr2 [ > > > > disksim_bus bus2 [ > > > > disksim_disk disk2 [] > > > > ] # end of bus2 > > > > ], # end of ctlr2 > > > > > > > > disksim_ctlr ctlr3 [ > > > > disksim_bus bus3 [ > > > > disksim_disk disk3 [] > > > > ] # end of bus3 > > > > ], # end of ctlr3 > > > > > > > > disksim_ctlr ctlr4 [ > > > > disksim_bus bus4 [ > > > > disksim_disk disk4 [] > > > > ] # end of bus4 > > > > ], # end of ctlr4 > > > > > > > > disksim_ctlr ctlr5 [ > > > > disksim_bus bus5 [ > > > > disksim_disk disk5 [] > > > > ] # end of bus5 > > > > ], # end of ctlr5 > > > > > > > > disksim_ctlr ctlr6 [ > > > > disksim_bus bus6 [ > > > > disksim_disk disk6 [] > > > > ] # end of bus6 > > > > ], # end of ctlr6 > > > > > > > > disksim_ctlr ctlr7 [ > > > > disksim_bus bus7 [ > > > > disksim_disk disk7 [] > > > > ] # end of bus7 > > > > ], # end of ctlr7 > > > > > > > > disksim_ctlr ctlr8 [ > > > > disksim_bus bus8 [ > > > > disksim_disk disk8 [] > > > > ] # end of bus8 > > > > ], # end of ctlr8 > > > > > > > > disksim_ctlr ctlr9 [ > > > > disksim_bus bus9 [ > > > > disksim_disk disk9 [] > > > > ] # end of bus9 > > > > ], # end of ctlr9 > > > > > > > > disksim_ctlr ctlr10 [ > > > > disksim_bus bus10 [ > > > > disksim_disk disk10 [] > > > > ] # end of bus10 > > > > ], # end of ctlr10 > > > > > > > > disksim_ctlr ctlr11 [ > > > > disksim_bus bus11 [ > > > > disksim_disk disk11 [] > > > > ] # end of bus11 > > > > ],# end of ctlr11 > > > > > > > > disksim_ctlr ctlr12 [ > > > > disksim_bus bus12 [ > > > > disksim_disk disk12 [] > > > > ] # end of bus12 > > > > ], # end of ctlr12 > > > > > > > > disksim_ctlr ctlr13 [ > > > > disksim_bus bus13 [ > > > > disksim_disk disk13 [] > > > > ] # end of bus13 > > > > ], # end of ctlr13 > > > > > > > > disksim_ctlr ctlr14 [ > > > > disksim_bus bus14 [ > > > > disksim_disk disk14 [] > > > > ] # end of bus14 > > > > ], # end of ctlr14 > > > > > > > > disksim_ctlr ctlr15 [ > > > > disksim_bus bus15 [ > > > > disksim_disk disk15 [] > > > > ] # end of bus15 > > > > ], # end of ctlr15 > > > > > > > > disksim_ctlr ctlr16 [ > > > > disksim_bus bus16 [ > > > > disksim_disk disk16 [] > > > > ] # end of bus16 > > > > ], # end of ctlr16 > > > > > > > > disksim_ctlr ctlr17 [ > > > > disksim_bus bus17 [ > > > > disksim_disk disk17 [] > > > > ] # end of bus17 > > > > ], # end of ctlr17 > > > > > > > > disksim_ctlr ctlr18 [ > > > > disksim_bus bus18 [ > > > > disksim_disk disk18 [] > > > > ] # end of bus18 > > > > ], # end of ctlr18 > > > > > > > > disksim_ctlr ctlr19 [ > > > > disksim_bus bus19 [ > > > > disksim_disk disk19 [] > > > > ] # end of bus19 > > > > ], # end of ctlr19 > > > > > > > > disksim_ctlr ctlr20 [ > > > > disksim_bus bus20 [ > > > > disksim_disk disk20 [] > > > > ] # end of bus20 > > > > ] # end of ctlr20 > > > > > > > > ] # end of outerbus > > > > ] # end of driver0 > > > > # end of system topology > > > ----------------------------------------------------------------------------------------------------- > > > > ________________________________ > > > > 2007-10-19 > > _______________________________________________ > > Disksim-users mailing list > > Disksim-users at ece.cmu.edu > > https://sos.ece.cmu.edu/mailman/listinfo/disksim-users > > > > > _______________________________________________ > Disksim-users mailing list > Disksim-users at ece.cmu.edu > https://sos.ece.cmu.edu/mailman/listinfo/disksim-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 14.gif Type: image/gif Size: 1662 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Mingqiang LI.vcf Type: text/x-vcard Size: 141 bytes Desc: not available URL: From keepeffort at naver.com Fri Oct 19 05:25:32 2007 From: keepeffort at naver.com (=?US-ASCII?B?a2VlcGVmZm9ydA==?=) Date: Fri, 19 Oct 2007 18:25:32 +0900 Subject: [Disksim-users] Question about vitual disk simulation. Message-ID: <864507c401b735047beecbe8308dabab@i61797> Hi all, I'm going to simulate 'mydisk.c'. I want to simulate for general disk simulation results that seek time, rotation time and access time. According to DiskSim manual, I should input 6 arguments at the prompt line. On the other hand, I should input these arguments disksim(executable) at my DiskSim test simulation source of main(). But, I don't know what arguments are inputted at prompt line. I have been tryed variable ways, but it was not executed with 'segmentation fault' error. What should I input the 6 arguments? Please explain to me with some successful examples. Thanks alot ! Best regards, YG -------------- next part -------------- An HTML attachment was scrubbed... URL: From keepeffort at naver.com Fri Oct 19 05:32:00 2007 From: keepeffort at naver.com (=?US-ASCII?B?a2VlcGVmZm9ydA==?=) Date: Fri, 19 Oct 2007 18:32:00 +0900 Subject: [Disksim-users] Question about vitual disk simulation(modified). Message-ID: <4fb9f0429e2b87684713d550951376b8@i61826> Hi all, I'm going to simulate 'mydisk.c'. I want to simulate for general disk simulation results that seek time, rotation time and access time. According to DiskSim manual, I should input 6 arguments at the prompt line. On the other hand, I should input these arguments disksim(executable) at my DiskSim test simulation source of main(). But, I don't know what arguments are inputted at prompt line. I have been tryed variable ways, but it was not executed with 'segmentation fault' error. What should I input the 6 arguments? Please explain to me with some successful examples. Thanks alot ! Best regards, YG -------------- next part -------------- An HTML attachment was scrubbed... URL: From keepeffort at naver.com Fri Oct 19 05:55:51 2007 From: keepeffort at naver.com (=?US-ASCII?B?a2VlcGVmZm9ydA==?=) Date: Fri, 19 Oct 2007 18:55:51 +0900 Subject: [Disksim-users] Question about vitual disk simulation(modified). Message-ID: Hi all, I'm going to simulate 'mydisk.c'. I want to simulate for general disk simulation results that seek time, rotation time and access time. According to DiskSim manual, I should input 6 arguments at the prompt line. On the other hand, I should input these arguments disksim(executable) [param file] [trace file] [fileinfo file] [output file] [cache size] at my DiskSim test simulation source of main(). But, I don't know what arguments are inputted at prompt line. I have been tryed variable ways, but it was not executed with 'segmentation fault' error. What should I input the 6 arguments? Please explain to me with some successful examples. Thanks alot ! Best regards, YG ---------------- P.S. Sorry for same questions are duplicated. I didn't expectate that some of literatures are filteringed. So several words are not written. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brucezhezhang at gmail.com Thu Oct 25 17:00:45 2007 From: brucezhezhang at gmail.com (Zhe Zhang) Date: Thu, 25 Oct 2007 17:00:45 -0400 Subject: [Disksim-users] Saturation in DISKSIM_malloc() Message-ID: <1d34988d0710251400x53fde316mefbd517c6d4bb6ec@mail.gmail.com> Hi, I'm using DiskSim-2.0 with the "Seagate Cheetah 9LP" disk listed on the DiskSim website. It works fine with some traces, but for some other more intensive traces (intervals b/w requests are short), it gives me a lot of "Stopping simulation because of saturation" error messages, and the simulation finally stops running. I tried allocating more space for disksim by using a larger number for the 2nd parameter of the function disksim_interface_initialize(disk, len, paramFile, outFile), but still the saturation errors will kill the simulation. The difference is, if I use larger len value, more saturation error messages will be printed before the simulation is stopped. Thanks for any help/suggestions. Zhe Zhang From ll2 at rice.edu Thu Oct 25 17:11:13 2007 From: ll2 at rice.edu (Lanyue Lu) Date: Thu, 25 Oct 2007 16:11:13 -0500 Subject: [Disksim-users] Saturation in DISKSIM_malloc() References: <1d34988d0710251400x53fde316mefbd517c6d4bb6ec@mail.gmail.com> Message-ID: <200710251611130156891@rice.edu> Hi, In disksim_logorg.c, there is a macro: MAX_QUEUE_LENGTH 100000, which is the limit of the number of outstanding request in the system. If you request rate is too high, after some time, the number of outstanding requests will be bigger than 100000, then you get the error. The source code related to this is in the function: "static void logorg_mapreqeust_update_stats() " in disksim_logorg.c. Lanyue Lu Rice University ------------------------------------------------------------- ????Zhe Zhang ?????2007-10-25 16:01:09 ????disksim-users at ece.cmu.edu ??? ???[Disksim-users] Saturation in DISKSIM_malloc() Hi, I'm using DiskSim-2.0 with the "Seagate Cheetah 9LP" disk listed on the DiskSim website. It works fine with some traces, but for some other more intensive traces (intervals b/w requests are short), it gives me a lot of "Stopping simulation because of saturation" error messages, and the simulation finally stops running. I tried allocating more space for disksim by using a larger number for the 2nd parameter of the function disksim_interface_initialize(disk, len, paramFile, outFile), but still the saturation errors will kill the simulation. The difference is, if I use larger len value, more saturation error messages will be printed before the simulation is stopped. Thanks for any help/suggestions. Zhe Zhang _______________________________________________ Disksim-users mailing list Disksim-users at ece.cmu.edu https://sos.ece.cmu.edu/mailman/listinfo/disksim-users From brucezhezhang at gmail.com Thu Oct 25 17:24:28 2007 From: brucezhezhang at gmail.com (Zhe Zhang) Date: Thu, 25 Oct 2007 17:24:28 -0400 Subject: [Disksim-users] Saturation in DISKSIM_malloc() In-Reply-To: <200710251611130156891@rice.edu> References: <1d34988d0710251400x53fde316mefbd517c6d4bb6ec@mail.gmail.com> <200710251611130156891@rice.edu> Message-ID: <1d34988d0710251424m36994859s26c4e749f716bea7@mail.gmail.com> Hi Lanyue, Thanks for the reply. In my copy of disksim the MAX_QUEUE_LENGTH is 10,000 instead of 100,000. No wonder I got a lot of saturation errors =( It seems my original question was wrong. The saturation is not about DISKSIM_Malloc(). On 10/25/07, Lanyue Lu wrote: > > Hi, > > In disksim_logorg.c, there is a macro: MAX_QUEUE_LENGTH 100000, which is the limit of the number of outstanding > request in the system. > > If you request rate is too high, after some time, the number of outstanding requests will be bigger than 100000, > then you get the error. > > The source code related to this is in the function: "static void logorg_mapreqeust_update_stats() " in disksim_logorg.c. > > Lanyue Lu > > Rice University > > > > ------------------------------------------------------------- > ????Zhe Zhang > ?????2007-10-25 16:01:09 > ????disksim-users at ece.cmu.edu > ??? > ???[Disksim-users] Saturation in DISKSIM_malloc() > > Hi, > > I'm using DiskSim-2.0 with the "Seagate Cheetah 9LP" disk listed on > the DiskSim website. > It works fine with some traces, but for some other more intensive > traces (intervals b/w > requests are short), it gives me a lot of "Stopping simulation because > of saturation" error > messages, and the simulation finally stops running. > > I tried allocating more space for disksim by using a larger number for > the 2nd parameter > of the function disksim_interface_initialize(disk, len, paramFile, > outFile), but still the saturation > errors will kill the simulation. The difference is, if I use larger > len value, more saturation error > messages will be printed before the simulation is stopped. > > Thanks for any help/suggestions. > > Zhe Zhang > _______________________________________________ > Disksim-users mailing list > Disksim-users at ece.cmu.edu > https://sos.ece.cmu.edu/mailman/listinfo/disksim-users > > From keepeffort at naver.com Fri Oct 26 04:40:22 2007 From: keepeffort at naver.com (=?US-ASCII?B?a2VlcGVmZm9ydA==?=) Date: Fri, 26 Oct 2007 17:40:22 +0900 Subject: [Disksim-users] DiskSim Argument Message-ID: <7de1107abf2c3f26a9e67a2b990ae7f7@i61827> Hi all, I have a question about argv[3]. I already read DiskSim manual but, I don't know that argv[3] is what kind of a file mean exactly. Some file in the "disksim-3.0 directory" or some "external" file? Please any advice for me. I'll very appreciate your comment. Thanks~! Regards, YG -------------- next part -------------- An HTML attachment was scrubbed... URL: