Date: Sun, 15 Sep 2002 09:34:32 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Bruce Evans <bde@zeta.org.au>, cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern vfs_bio.c src/sys/sys bio.h Message-ID: <80183.1032075272@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 14 Sep 2002 17:42:25 PDT." <200209150042.g8F0gPF8053917@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <200209150042.g8F0gPF8053917@apollo.backplane.com>, Matthew Dillon w rites: >:> >:> Well, the buffer is owned at the time of the BIO_DONE and you have >:> a lock structure sitting right there, why not simply use the >:> lock structure's interlock? Note I said 'interlock' here, not the >:> main lock. >: >:struct bio != struct buf >: >:-- >:Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 > > Well, so? struct bio has access to struct buf via _bio_buf. Only some struct bio's come from a struct buf. > I do not think a timeout is a good solution. I don't care what you think until you have at least found out what what we are talking about here. You could start out by finding the places which call biowait() in the first place, then you'll probably (no guarantees) see how marginal the issue under discussion is. Preferably you'll just leave me alone instead. -- 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 cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80183.1032075272>