Fw: Re: Implemented OPLOCK for FreeBsd

Jonathan Lemon jlemon at flugsvamp.com
Fri Sep 7 20:01:05 GMT 2001

On Fri, Sep 07, 2001 at 05:36:31PM -0700, Jeremy Allison wrote:
> On Fri, Sep 07, 2001 at 05:32:50PM -0700, John Baldwin wrote:
> > After all, as an engineer, you _do_ want to write well-designed and implemented
> > portable code, yes?  The same concept applies to supporting multiple
> > architectures in an operating system to ensure your machine independent code is
> > truly MI.  Well, you have an oplock abstraction, so your oplock using code
> > should be oplock implementation independent.
> It's not Samba I really care about here. It's other apps
> who might want to use this interface who will now have to
> choose between the Linux and FreeBSD flavours (and who
> knows what Open/Net/BSDi/OSX will choose - maybe they'll
> want to "do it their own technically correct way").

Well, NetBSD and OpenBSD already have kqueue, so I'm fairly confident
that they can add in a kq'd oplock fairly quickly.  Heck, I'll just 
give them the code.

BSDi, dunno.  OSX, we're working on.  :-)

More information about the samba-technical mailing list