Date: Mon, 7 Apr 2003 12:09:26 +0400 (MSD) From: Igor Sysoev <is@rambler-co.ru> To: Terry Lambert <tlambert2@mindspring.com> Cc: freebsd-arch@freebsd.org Subject: Re: libthr and 1:1 threading. Message-ID: <Pine.BSF.4.21.0304071202520.40397-100000@is> In-Reply-To: <3E8CAD52.531E0A9@mindspring.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 3 Apr 2003, Terry Lambert wrote: > Igor Sysoev wrote: > > So I think programmers never use this flag and select()/etc for disk > > files (because it's useless) and I think supporting this flag for disk > > files should not break existent software. > > But of course it creates portability problems. > > For FreeBSD's libc_r? You have got to be kidding, when you talk > about portability of FreeBSD's libc_r! > > The effect in the old sigsched threads implementation from the > comp.sources.unix archive would merely be to provide a latency > optimization on the OS's which support it. > > I think that there is no portability problem; only that it would > cause some software to run faster on FreeBSD than on other OS's, > were it to be used. No, I do not mean portability of libc_r. I mean that if FreeBSD would support select() for disk files there can be the programs that will use this feature directly without any wrappers and these programs would have the portability problems. It's something like some Linux programs use a specific signal behaviour of Linux clone()d pthreads. Igor Sysoev http://sysoev.ru/en/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0304071202520.40397-100000>