From 258908913 at qq.com Thu Jun 2 09:34:29 2011 From: 258908913 at qq.com (=?gbk?B?c21pbGU=?=) Date: Thu, 2 Jun 2011 21:34:29 +0800 Subject: [Disksim-users] help--what does it mean in parv file? Message-ID: hi,all 1?what does "element_stride_page" mean?I change it ,but the result is not change. 2?If I want to set the size of generated random write request,how to modify the parameter ? What does "Sizes=[exponential,0.0,8.0]" mean in disksim_synthgen ? best regards! -------------- next part -------------- An HTML attachment was scrubbed... URL: From Joseph.Emeras at imag.fr Thu Jun 9 10:55:45 2011 From: Joseph.Emeras at imag.fr (Joseph Emeras) Date: Thu, 09 Jun 2011 16:55:45 +0200 Subject: [Disksim-users] error when compiling disksim 4.0 Message-ID: <4DF0DEF1.9010608@imag.fr> Hello, I'm trying to use disksim but I have this error when trying to compile it: disksim_iosim.c: In function ?io_initialize?: disksim_iosim.c:712: error: duplicate case value disksim_iosim.c:712: error: previously used here make[1]: *** [disksim_iosim.o] Error 1 make[1]: Leaving directory `/home/emeras/disksim-4.0/src' make: *** [all] Error 2 I'm running a debian squeeze with gcc 4.4.5-1 If anyone has an idea... Thank you very much for your help. Regards -- Joseph Emeras Phd Student Mescal Team - INRIA / LIG +33476612079 +33680913254 http://mescal.imag.fr -- Joseph Emeras Phd Student Mescal Team - INRIA / LIG +33476612079 +33680913254 http://mescal.imag.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From vahldiek at mpi-sws.org Thu Jun 9 11:25:07 2011 From: vahldiek at mpi-sws.org (Anjo Vahldiek) Date: Thu, 09 Jun 2011 17:25:07 +0200 Subject: [Disksim-users] error when compiling disksim 4.0 In-Reply-To: <4DF0DEF1.9010608@imag.fr> References: <4DF0DEF1.9010608@imag.fr> Message-ID: <4DF0E5D3.9080504@mpi-sws.org> Hi, The problem you're describing is caused by the 64bit OS you're using. You will find in the mailing list archive several threads about 64bit compiling problems and how they are solved. (e.g. changing to a 32bit machine, using -m32 flag for gcc, ...) Hope this helps... Anjo On 09.06.2011 16:55, Joseph Emeras wrote: > Hello, > > I'm trying to use disksim but I have this error when trying to compile > it: > > disksim_iosim.c: In function ?io_initialize?: > disksim_iosim.c:712: error: duplicate case value > disksim_iosim.c:712: error: previously used here > make[1]: *** [disksim_iosim.o] Error 1 > make[1]: Leaving directory `/home/emeras/disksim-4.0/src' > make: *** [all] Error 2 > > I'm running a debian squeeze with gcc 4.4.5-1 > If anyone has an idea... > > Thank you very much for your help. > > Regards > > -- > Joseph Emeras > Phd Student > Mescal Team - INRIA / LIG > +33476612079 > +33680913254 > http://mescal.imag.fr > > > -- > Joseph Emeras > Phd Student > Mescal Team - INRIA / LIG > +33476612079 > +33680913254 > http://mescal.imag.fr > > > _______________________________________________ > 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: From catblade at gmail.com Thu Jun 9 11:43:14 2011 From: catblade at gmail.com (Marlow Weston) Date: Thu, 9 Jun 2011 08:43:14 -0700 Subject: [Disksim-users] error when compiling disksim 4.0 In-Reply-To: <4DF0E5D3.9080504@mpi-sws.org> References: <4DF0DEF1.9010608@imag.fr> <4DF0E5D3.9080504@mpi-sws.org> Message-ID: Oh, right, you can get a 64bit disksim patch here: http://code.google.com/p/sst-simulator/downloads/list I really should have announced this earlier. It should work. If it doesn't, please tell me, as I wrote it. Thanks, --Marlow 2011/6/9 Anjo Vahldiek : > Hi, > > The problem you're describing is caused by the 64bit OS you're using. You > will find in the mailing list archive several threads about 64bit compiling > problems and how they are solved. (e.g. changing to a 32bit machine, using > -m32 flag for gcc, ...) > > Hope this helps... > > Anjo > > On 09.06.2011 16:55, Joseph Emeras wrote: > > Hello, > > I'm trying to use disksim but I have this error when trying to compile it: > > disksim_iosim.c: In function ?io_initialize?: > disksim_iosim.c:712: error: duplicate case value > disksim_iosim.c:712: error: previously used here > make[1]: *** [disksim_iosim.o] Error 1 > make[1]: Leaving directory `/home/emeras/disksim-4.0/src' > make: *** [all] Error 2 > > I'm running a debian squeeze with gcc 4.4.5-1 > If anyone has an idea... > > Thank you very much for your help. > > Regards > > -- > Joseph Emeras > Phd Student > Mescal Team - INRIA / LIG > +33476612079 > +33680913254 > http://mescal.imag.fr > > > -- > Joseph Emeras > Phd Student > Mescal Team - INRIA / LIG > +33476612079 > +33680913254 > http://mescal.imag.fr > > > _______________________________________________ > 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 Joseph.Emeras at imag.fr Thu Jun 9 11:53:46 2011 From: Joseph.Emeras at imag.fr (Joseph Emeras) Date: Thu, 09 Jun 2011 17:53:46 +0200 Subject: [Disksim-users] error when compiling disksim 4.0 In-Reply-To: References: <4DF0DEF1.9010608@imag.fr> <4DF0E5D3.9080504@mpi-sws.org> Message-ID: <4DF0EC8A.1020302@imag.fr> Yes indeed, it worked perfectly... Thank you very much for your help here :-) Regards On 06/09/2011 05:43 PM, Marlow Weston wrote: > Oh, right, you can get a 64bit disksim patch here: > http://code.google.com/p/sst-simulator/downloads/list > > I really should have announced this earlier. > > It should work. If it doesn't, please tell me, as I wrote it. > > Thanks, > --Marlow > > > 2011/6/9 Anjo Vahldiek: > >> Hi, >> >> The problem you're describing is caused by the 64bit OS you're using. You >> will find in the mailing list archive several threads about 64bit compiling >> problems and how they are solved. (e.g. changing to a 32bit machine, using >> -m32 flag for gcc, ...) >> >> Hope this helps... >> >> Anjo >> >> On 09.06.2011 16:55, Joseph Emeras wrote: >> >> Hello, >> >> I'm trying to use disksim but I have this error when trying to compile it: >> >> disksim_iosim.c: In function ?io_initialize?: >> disksim_iosim.c:712: error: duplicate case value >> disksim_iosim.c:712: error: previously used here >> make[1]: *** [disksim_iosim.o] Error 1 >> make[1]: Leaving directory `/home/emeras/disksim-4.0/src' >> make: *** [all] Error 2 >> >> I'm running a debian squeeze with gcc 4.4.5-1 >> If anyone has an idea... >> >> Thank you very much for your help. >> >> Regards >> >> -- >> Joseph Emeras >> Phd Student >> Mescal Team - INRIA / LIG >> +33476612079 >> +33680913254 >> http://mescal.imag.fr >> >> >> -- >> Joseph Emeras >> Phd Student >> Mescal Team - INRIA / LIG >> +33476612079 >> +33680913254 >> http://mescal.imag.fr >> >> >> _______________________________________________ >> 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 >> >> >> > _______________________________________________ > Disksim-users mailing list > Disksim-users at ece.cmu.edu > https://sos.ece.cmu.edu/mailman/listinfo/disksim-users > > -- Joseph Emeras Phd Student Mescal Team - INRIA / LIG +33476612079 +33680913254 http://mescal.imag.fr From rmohanx at yahoo.com Thu Jun 9 12:46:49 2011 From: rmohanx at yahoo.com (Ross Mohan) Date: Thu, 9 Jun 2011 09:46:49 -0700 (PDT) Subject: [Disksim-users] work with SSD? In-Reply-To: Message-ID: <274448.4134.qm@web30805.mail.mud.yahoo.com> Hello, ? List newbie, so this may be a repeat question. ? Anyone familiar with using DiskSim on SSD? (NAND). ? I know there's an MS-provided package for SSD support. ? I am asking whether anyone has successfuly analysed SSD usage, layout, etc using DiskSim. ? Thanks in Advance, ? Ross -------------- next part -------------- An HTML attachment was scrubbed... URL: From haghdoost at gmail.com Fri Jun 10 04:24:38 2011 From: haghdoost at gmail.com (Alireza Haghdoost) Date: Fri, 10 Jun 2011 12:54:38 +0430 Subject: [Disksim-users] error when compiling disksim 4.0 In-Reply-To: <4DF0DEF1.9010608@imag.fr> References: <4DF0DEF1.9010608@imag.fr> Message-ID: I think you are compiling on 64-bit machine. Try 32-bit machine or other gcc version Alireza Haghdoost Graduate Student Department of Computer Engineering Sharif University of Technology http://ce.sharif.edu/~haghdoost Phone: (98) (21) 6616 6689 2011/6/9 Joseph Emeras > Hello, > > I'm trying to use disksim but I have this error when trying to compile it: > > disksim_iosim.c: In function ?io_initialize?: > disksim_iosim.c:712: error: duplicate case value > disksim_iosim.c:712: error: previously used here > make[1]: *** [disksim_iosim.o] Error 1 > make[1]: Leaving directory `/home/emeras/disksim-4.0/src' > make: *** [all] Error 2 > > I'm running a debian squeeze with gcc 4.4.5-1 > If anyone has an idea... > > Thank you very much for your help. > > Regards > > -- > Joseph Emeras > Phd Student > Mescal Team - INRIA / LIG > +33476612079 > +33680913254 > http://mescal.imag.fr > > > -- > Joseph Emeras > Phd Student > Mescal Team - INRIA / LIG > +33476612079 > +33680913254http://mescal.imag.fr > > > _______________________________________________ > 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: From heshuibing at gmail.com Mon Jun 13 05:13:41 2011 From: heshuibing at gmail.com (heshuibing) Date: Mon, 13 Jun 2011 17:13:41 +0800 Subject: [Disksim-users] how to use cello99 trace Message-ID: <201106131713387902741@gmail.com> Hello: I'm trying to use the Hpl trace cello99. I have compiled the DataSeries and Lintel software followed the instructions at http://tesla.hpl.hp.com, I find the cello99 trace format is srt, but I can't install SRTlite software in my os. I want to know if I can use DataSeries to convert the trace without installing SRTlite, and how to do it? I want to analysis cello99 trace according the experiments in DFTL paper, and I alseo don't know how to do this, I'm running a Fedora core 14, If anyone has an idea... Thank you very much for your help. Regards Shuibing He -------------- next part -------------- An HTML attachment was scrubbed... URL: From liuzhuo9090 at gmail.com Thu Jun 16 12:19:24 2011 From: liuzhuo9090 at gmail.com (liu zhuo) Date: Thu, 16 Jun 2011 10:19:24 -0600 Subject: [Disksim-users] How to get the Perk Throughput of A storage system Message-ID: Hello, everyone! I want to measure the storage system's peak throughput under a certain pattern of workloads (e.g., 4K, sequential, 100% read) ? Just like what IOmeter and IOzone do to a actual storage system. How can I accomplish this with DiskSim? Thanks very much, Zhuo ------------------------------ -- Zhuo Liu -------------- next part -------------- An HTML attachment was scrubbed... URL: From linxingnku at gmail.com Fri Jun 17 14:06:46 2011 From: linxingnku at gmail.com (Xing Lin) Date: Fri, 17 Jun 2011 12:06:46 -0600 Subject: [Disksim-users] [patch] root Makefile Message-ID: Hi, This is a small patch for the root Makefile in DiskSim 4.0 with dixtrac included. commit e5953f57754e36fdbf2ba3803f619fffee9530ad Author: Xing Lin Date: Fri Jun 17 11:53:15 2011 -0600 Added checking for the existence of dixtract dir for clean and distclean. diff --git a/Makefile b/Makefile index 3182db7..d075900 100644 --- a/Makefile +++ b/Makefile @@ -47,12 +47,16 @@ clean: for d in $(SUBDIRS); do \ $(MAKE) -C $$d $@; \ done + if [ -d dixtrac ]; then $(MAKE) -C dixtrac $@; fi distclean: clean rm -f *~ for d in $(SUBDIRS); do \ $(MAKE) -C $$d $@; \ done + if [ -d dixtrac ]; then $(MAKE) -C dixtrac $@; fi .PHONY: doc doc: -- Regards, Xing School of Computing, University of Utah http://www.cs.utah.edu/~xinglin/ From dahlawi at IEEE.ORG Sat Jun 25 02:51:09 2011 From: dahlawi at IEEE.ORG (Al-Dahlawi) Date: Sat, 25 Jun 2011 02:51:09 -0400 Subject: [Disksim-users] SSD LBA & Request Size Message-ID: Greeting All I would like to simulate the SSD model using a real system generated I/O trace ... The problem is that Disksim/SSD Only accept LBA as multiple of 8s, the same for I/O request size !!!!. Any advise to get around this issue without jeopardizing the accuracy of the real trace ???? Thaaanks -- Abdullah Al-Dahlawi PhD Candidate George Washington University ---- Check The Fastest 500 Super Computers Worldwide http://www.top500.org/list/2010/06/100 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dahlawi at IEEE.ORG Sat Jun 25 22:47:03 2011 From: dahlawi at IEEE.ORG (Al-Dahlawi) Date: Sat, 25 Jun 2011 22:47:03 -0400 Subject: [Disksim-users] Max Addressable LBA in SSD Trace File Message-ID: Greeting All Does Any one know how to Calculate the MAX Addressable LBA that can be used in SSD Trace File given the PARV file below. ( 64 GB SSD) My Understanding is that the MAX LBA is calculated as follows 2048 Blocks * 8 Planes * 64 Pages * 8 Elements = 8388608 Pages in the SSD Abd Since each Page in SSD is 8 KB, Then it can hold 16 LBA of size 512 Bytes So the MAX addressable LBA is 8388608 * 16 = 134217728 HOWEVER, When I use this LBA in my SSD Trace File, I get an ERROR unexpected request location: devno 0, blkno 134217728, bcount 8 Assertion failed: simtime = 5297.450000 totalreqs = 3 disksim: disksim_logorg.c:763: logorg_maprequest: Assertion `logorgno != -1' failed. Any Feed Back ????? # --------------------------------------------------------- disksim_global Global { Init Seed = 42, Real Seed = 42, # Statistic warm-up period = 0.0 seconds, Stat definition file = statdefs } # --------------------------------------------------------- disksim_stats Stats { iodriver stats = disksim_iodriver_stats { Print driver size stats = 1, Print driver locality stats = 0, Print driver blocking stats = 0, Print driver interference stats = 0, Print driver queue stats = 1, Print driver crit stats = 0, Print driver idle stats = 1, Print driver intarr stats = 1, Print driver streak stats = 1, Print driver stamp stats = 1, Print driver per-device stats = 1 }, bus stats = disksim_bus_stats { Print bus idle stats = 1, Print bus arbwait stats = 1 }, ctlr stats = disksim_ctlr_stats { Print controller cache stats = 1, Print controller size stats = 1, Print controller locality stats = 1, Print controller blocking stats = 1, Print controller interference stats = 1, Print controller queue stats = 1, Print controller crit stats = 1, Print controller idle stats = 1, Print controller intarr stats = 1, Print controller streak stats = 1, Print controller stamp stats = 1, Print controller per-device stats = 1 }, device stats = disksim_device_stats { Print device queue stats = 0, Print device crit stats = 0, Print device idle stats = 0, Print device intarr stats = 0, Print device size stats = 0, Print device seek stats = 1, Print device latency stats = 1, Print device xfer stats = 1, Print device acctime stats = 1, Print device interfere stats = 0, Print device buffer stats = 1 }, process flow stats = disksim_pf_stats { Print per-process stats = 1, Print per-CPU stats = 1, Print all interrupt stats = 1, Print sleep stats = 1 } } # end of stats block # --------------------------------------------------------- #disksim_iosim IS { # I/O Trace Time Scale = 1.0 #} # end of iosim spec # --------------------------------------------------------- disksim_iodriver DRIVER0 { type = 1, Constant access time = 0.0, Scheduler = disksim_ioqueue { Scheduling policy = 3, Cylinder mapping strategy = 1, Write initiation delay = 0.0, Read initiation delay = 0.0, Sequential stream scheme = 0, Maximum concat size = 128, Overlapping request scheme = 0, Sequential stream diff maximum = 0, Scheduling timeout scheme = 0, Timeout time/weight = 6, Timeout scheduling = 4, Scheduling priority scheme = 0, Priority scheduling = 4 }, # end of Scheduler Use queueing in subsystem = 1 } # end of DRV0 spec # --------------------------------------------------------- disksim_bus BUSTOP { type = 1, Arbitration type = 1, Arbitration time = 0.0, Read block transfer time = 0.0, Write block transfer time = 0.0, Print stats = 1 } # end of BUSTOP spec # --------------------------------------------------------- disksim_bus BUSHBA { type = 2, Arbitration type = 1, Arbitration time = 0.001, # PCI-E, with 8 lanes with 8b/10b encoding gives 2.0 Gbps per # lane and with 8 lanes we get about 2.0 GBps. So, bulk sector # transfer time is about 0.238 us. SATA/300 can transfer data # at 300 MBps, which amounts to about 1.6276 us per byte. Read block transfer time = 0.0002384, Write block transfer time = 0.0002384, #Read block transfer time = 0.0016276, #Write block transfer time = 0.0016276, Print stats = 1 } # end of BUSHBA spec # --------------------------------------------------------- disksim_ctlr CTLR0 { type = 1, Scale for delays = 0.0, Bulk sector transfer time = 0.0, Maximum queue length = 100, Print stats = 1 } # end of CTLR0 spec # --------------------------------------------------------- # don't change the order of the following parameters. # we use Flash chip elements and Elements per gang to # find number of gang -- we need this info before initializing # the queue (disksim_ioqueue) ssdmodel_ssd SSD { # vp - this is a percentage of total pages in the ssd Reserve pages percentage = 15, # vp - min percentage of free blocks needed. if the free # blocks drop below this, cleaning kicks in Minimum free blocks percentage = 5, # vp - a simple read-modify-erase-write policy = 1 (no longer supported) # vp - osr write policy = 2 Write policy = 2, # vp - random = 1 (not supp), greedy = 2, wear-aware = 3 Cleaning policy = 2, # vp - number of planes in each flash package (element) Planes per package = 8, # vp - number of flash blocks in each plane Blocks per plane = 2048, # vp - how the blocks within an element are mapped on a plane # simple concatenation = 1, plane-pair stripping = 2 (not tested), # full stripping = 3 Plane block mapping = 3, # vp - copy-back enabled (1) or not (0) Copy back = 1, # how many parallel units are there? # entire elem = 1, two dies = 2, four plane-pairs = 4 Number of parallel units = 1, # vp - we use diff allocation logic: chip/plane # each gang = 0, each elem = 1, each plane = 2 Allocation pool logic = 1, # elements are grouped into a gang Elements per gang = 1, # shared bus (1) or shared control (2) gang Gang share = 1, # when do we want to do the cleaning? Cleaning in background = 0, Command overhead = 0.00, Bus transaction latency = 0.0, # Assuming PCI-E, with 8 lanes with 8b/10b encoding. # This gives 2.0 Gbps per lane and with 8 lanes we get about # 2.0 GBps. So, bulk sector transfer time is about 0.238 us. # Use the "Read block transfer time" and "Write block transfer time" # from disksim_bus above. Bulk sector transfer time = 0, Flash chip elements = 8, Page size = 8, Pages per block = 64, # vp - changing the no of blocks from 16184 to 16384 Blocks per element = 16384, Element stride pages = 1, Never disconnect = 1, Print stats = 1, Max queue length = 20, Scheduler = disksim_ioqueue { Scheduling policy = 1, Cylinder mapping strategy = 0, Write initiation delay = 0, Read initiation delay = 0.0, Sequential stream scheme = 0, Maximum concat size = 0, Overlapping request scheme = 0, Sequential stream diff maximum = 0, Scheduling timeout scheme = 0, Timeout time/weight = 0, Timeout scheduling = 0, Scheduling priority scheme = 0, Priority scheduling = 1 }, Timing model = 1, # vp changing the Chip xfer latency from per sector to per byte Chip xfer latency = 0.000025, Page read latency = 0.025, Page write latency = 0.200, Block erase latency = 1.5 } # end of SSD spec # --------------------------------------------------------- # HP_C3323A source atlas10k.diskspecs source ibm18es.diskspecs source cheetah9LP.diskspecs # --------------------------------------------------------- # component instantiation instantiate [ statfoo ] as Stats instantiate [ ssd0x0 ] as SSD instantiate [ bustop ] as BUSTOP instantiate [ busHBA0 ] as BUSHBA instantiate [ driver0 ] as DRIVER0 instantiate [ ctlr0 ] as CTLR0 # --------------------------------------------------------- # system topology topology disksim_iodriver driver0 [ disksim_bus bustop [ disksim_ctlr ctlr0 [ disksim_bus busHBA0 [ ssdmodel_ssd ssd0x0 [] ] ] ] ] # no syncsets # --------------------------------------------------------- disksim_logorg org0 { Addressing mode = Array, Distribution scheme = Striped, Redundancy scheme = Noredun, # vp - added more ssd elements devices = [ ssd0x0 ], Stripe unit = 128, Synch writes for safety = 0, Number of copies = 2, Copy choice on read = 6, RMW vs. reconstruct = 0.5, Parity stripe unit = 128, Parity rotation type = 1, Time stamp interval = 0.000000, Time stamp start time = 60000.000000, Time stamp stop time = 10000000000.000000, Time stamp file name = stamps } # end of logorg org0 spec #-------------------------------------------------------------- -------------------------------- -- Abdullah Al-Dahlawi ---- Check The Fastest 500 Super Computers Worldwide http://www.top500.org/list/2010/06/100 -------------- next part -------------- An HTML attachment was scrubbed... URL: From dahlawi at IEEE.ORG Sun Jun 26 13:41:11 2011 From: dahlawi at IEEE.ORG (Al-Dahlawi) Date: Sun, 26 Jun 2011 13:41:11 -0400 Subject: [Disksim-users] SOLVED Max Addressable LBA in SSD Trace File Message-ID: Hi Thanks for your clarification ... based on my current parameters in parv file Pages Per Block = 64 Blocks Per Plane = 2048 Planes Per Element = 8 Page Size = 8 sectors = 4 KB So ... Pages Per Single Element = 1 (Element) * 8 (planes) * 2048 (Blocks) * 64 (Pages) = 1048576 Pages Each Page is 8 Sectors ---> which means the MAX Addressable Sector = 1048576 * 8 = 8388608 - 1 = 0 .. 8388607 Sectors NOW the Important issue the the MAX VALID (Address, Req Size) Combination which is as follows ... 5265.313 0 8388599 8 0 ( 8388607 - 8 = 8388599) is the MAX Valid I/O Trace (Address, Req Size) Combination -- TESTED with disksim successfully 5265.313 0 8388600 8 0 will generate ERROR with disksim cause it exceeds the MAX (Address, Req Size) unexpected request location: devno 0, blkno 8388600, bcount 8 Assertion failed: simtime = 5265.313000 totalreqs = 1 disksim: disksim_logorg.c:763: logorg_maprequest: Assertion `logorgno != -1' failed. The same concept is applicable if we change the Req size to 16 5265.313 0 8388591 16 0 work Successfully 5265.313 0 8388592 16 0 Error !! .. unexpected request location: devno 0, blkno 8388592, bcount 16 Assertion failed: simtime = 5265.313000 totalreqs = 1 disksim: disksim_logorg.c:763: logorg_maprequest: Assertion `logorgno != -1' failed. Final observation The MAX VALID (Address, Req Size) will increase with an additional element added in the parv file On Sun, Jun 26, 2011 at 11:28 AM, f.rajaei wrote: > its 8 sector which equals 4 KB not 8 K. all sizes in parv file are based on > sector not KB. I am sure about it. > > > On Sun, Jun 26, 2011 at 7:23 AM, Al-Dahlawi wrote: > >> Hi >> >> Page size is fixed and = 8 K as shown in the parv file below !!! >> >> >> On Sunday, June 26, 2011, f.rajaei wrote: >> > each page is 4kb or 8 sector. that is why you get this error >> > >> > 2011/6/25 Al-Dahlawi >> > >> > Greeting All >> > >> > Does Any one know how to Calculate the MAX Addressable LBA that can be >> used in SSD Trace File given the PARV file below. ( 64 GB SSD) >> > >> > My Understanding is that the MAX LBA is calculated as follows >> > >> > 2048 Blocks * 8 Planes * 64 Pages * 8 Elements = 8388608 Pages in the >> SSD >> > >> > Abd Since each Page in SSD is 8 KB, Then it can hold 16 LBA of size 512 >> Bytes >> > >> > So the MAX addressable LBA is 8388608 * 16 = 134217728 >> > >> > HOWEVER, When I use this LBA in my SSD Trace File, I get an ERROR >> > >> > unexpected request location: devno 0, blkno 134217728, bcount 8 >> > >> > Assertion failed: >> > simtime = 5297.450000 >> > totalreqs = 3 >> > disksim: disksim_logorg.c:763: logorg_maprequest: Assertion `logorgno != >> -1' failed. >> > >> > >> > Any Feed Back ????? >> > >> > # --------------------------------------------------------- >> > disksim_global Global { >> > Init Seed = 42, >> > Real Seed = 42, >> > # Statistic warm-up period = 0.0 seconds, >> > Stat definition file = statdefs >> > } >> > # --------------------------------------------------------- >> > disksim_stats Stats { >> > >> > iodriver stats = disksim_iodriver_stats { >> > Print driver size stats = 1, >> > Print driver locality stats = 0, >> > Print driver blocking stats = 0, >> > Print driver interference stats = 0, >> > Print driver queue stats = 1, >> > Print driver crit stats = 0, >> > Print driver idle stats = 1, >> > Print driver intarr stats = 1, >> > Print driver streak stats = 1, >> > Print driver stamp stats = 1, >> > Print driver per-device stats = 1 }, >> > >> > bus stats = disksim_bus_stats { >> > Print bus idle stats = 1, >> > Print bus arbwait stats = 1 }, >> > >> > ctlr stats = disksim_ctlr_stats { >> > Print controller cache stats = 1, >> > Print controller size stats = 1, >> > Print controller locality stats = 1, >> > Print controller blocking stats = 1, >> > Print controller interference stats = 1, >> > Print controller queue stats = 1, >> > Print controller crit stats = 1, >> > Print controller idle stats = 1, >> > Print controller intarr stats = 1, >> > Print controller streak stats = 1, >> > Print controller stamp stats = 1, >> > Print controller per-device stats = 1 }, >> > >> > device stats = disksim_device_stats { >> > Print device queue stats = 0, >> > Print device crit stats = 0, >> > Print device idle stats = 0, >> > Print device intarr stats = 0, >> > Print device size stats = 0, >> > Print device seek stats = 1, >> > Print device latency stats = 1, >> > Print device xfer stats = 1, >> > Print device acctime stats = 1, >> > Print device interfere stats = 0, >> > Print device buffer stats = 1 }, >> > >> > process flow stats = disksim_pf_stats { >> > Print per-process stats = 1, >> > Print per-CPU stats = 1, >> > Print all interrupt stats = 1, >> > Print sleep stats = 1 >> > } >> > } # end of stats block >> > # --------------------------------------------------------- >> > #disksim_iosim IS { >> > # I/O Trace Time Scale = 1.0 >> > #} # end of iosim spec >> > # --------------------------------------------------------- >> > disksim_iodriver DRIVER0 { >> > type = 1, >> > Constant access time = 0.0, >> > Scheduler = disksim_ioqueue { >> > Scheduling policy = 3, >> > Cylinder mapping strategy = 1, >> > Write initiation delay = 0.0, >> > Read initiation delay = 0.0, >> > Sequential stream scheme = 0, >> > Maximum concat size = 128, >> > Overlapping request scheme = 0, >> > Sequential stream diff maximum = 0, >> > Scheduling timeout scheme = 0, >> > Timeout time/weight = 6, >> > Timeout scheduling = 4, >> > Scheduling priority scheme = 0, >> > Priority scheduling = 4 >> > }, # end of Scheduler >> > Use queueing in subsystem = 1 >> > } # end of DRV0 spec >> > # --------------------------------------------------------- >> > disksim_bus BUSTOP { >> > type = 1, >> > Arbitration type = 1, >> > Arbitration time = 0.0, >> > Read block transfer time = 0.0, >> > Write block transfer time = 0.0, >> > Print stats = 1 >> > } # end of BUSTOP spec >> > # --------------------------------------------------------- >> > disksim_bus BUSHBA { >> > type = 2, >> > Arbitration type = 1, >> > Arbitration time = 0.001, >> > >> > # PCI-E, with 8 lanes with 8b/10b encoding gives 2.0 Gbps per >> > # lane and with 8 lanes we get about 2.0 GBps. So, bulk sector >> > # transfer time is about 0.238 us. SATA/300 can transfer data >> > # at 300 MBps, which amounts to about 1.6276 us per byte. >> > >> > Read block transfer time = 0.0002384, >> > Write block transfer time = 0.0002384, >> > #Read block transfer time = 0.0016276, >> > #Write block transfer time = 0.0016276, >> > >> > Print stats = 1 >> > } # end of BUSHBA spec >> > # --------------------------------------------------------- >> > disksim_ctlr CTLR0 { >> > type = 1, >> > Scale for delays = 0.0, >> > Bulk sector transfer time = 0.0, >> > Maximum queue length = 100, >> > Print stats = 1 >> > } # end of CTLR0 spec >> > # --------------------------------------------------------- >> > # don't change the order of the following parameters. >> > # we use Flash chip elements and Elements per gang to >> > # find number of gang -- we need this info before initializing >> > # the queue (di_______________________________________________ >> > Disksim-users mailing list >> > Disksim-users at ece.cmu.edu >> > https://sos.ece.cmu.edu/mailman/listinfo/disksim-users >> > >> > >> > >> >> -- >> Abdullah Al-Dahlawi >> PhD Candidate >> High Performance Computing LAB >> Department. Of Electrical & Computer Engineering >> George Washington University >> ---- >> Check The Fastest 500 Super Computers Worldwide >> http://www.top500.org/list/2010/06/100 >> > > -- Abdullah Al-Dahlawi PhD Candidate High Performance Computing LAB Department. Of Electrical & Computer Engineering George Washington University ---- Check The Fastest 500 Super Computers Worldwide http://www.top500.org/list/2010/06/100 -------------- next part -------------- An HTML attachment was scrubbed... URL: