Date: Sat, 16 Jun 2001 04:41:50 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: jdscol92@etri.re.kr Cc: freebsd-fs@FreeBSD.ORG Subject: Re: =?euc-kr?B?W8D8w7zIuL3FXSBSZTogJ2JfZGVwJyBpbiBidWZmZXIgc3RydWN0?= =?euc-kr?B?dXJlLi4uLj8/?= Message-ID: <83997.992659310@critter> In-Reply-To: Your message of "Sat, 16 Jun 2001 09:22:47 %2B0900." <766FA1FC5C2AD511B3C800D0B7A8AC4A391289@cms3.etri.re.kr>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <766FA1FC5C2AD511B3C800D0B7A8AC4A391289@cms3.etri.re.kr>, jdscol92@etri.re.kr writes: OK, now I understand your question better. >> What does the code, 'b_dep!=NULL or b_dep==NULL', mean? b_dep is used by softupdates to keep track of things which must be written before other things. Various places in the I/O system needs to fiddle with that in order to do the right thing. >3. Which routine is called when buffer's data is written to the disk( due >to 'bwrite' or write back )?? >I have found bwrite(), bdwrite(), bawrite() etc..routines, but I don't know >which routine does actually write buffer's data to disk. >Does 'softdep_disk_write_complete()' routine in 'bio_ops bioops' structure >write buffer's data to disk ?? Eventually, it all has to pass through the specfs_strategy() routine. The code paths through struct buf and assorted code are twisted indeed, and I am not able to give a brief explanation. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?83997.992659310>