Re: Exploring locks in darwin
Re: Exploring locks in darwin
- Subject: Re: Exploring locks in darwin
- From: Yogesh P <email@hidden>
- Date: 15 Jan 2005 18:36:53 +0530
Hi Chris,
Yes we are trying to add snapshot to HFS+ and for the same purpose we
need to freeze the I/O's for initializing the snapshot.
What do u think will be the better approach for the freezing or locking
the I/O for achieving this functionality in HFS+???
Thanks,
YOGESH PAHILWAN
(SOFTWARE ENGINNER)
S P Software Technologies (I) Pvt. Ltd.
(An ISO 9001:2000 Company)
Pune, Maharashtra, India - 411 004.
Tel : 91-20-4006154, 4006983, 4007503.
Fax : 91-20-4006153.
Email : email@hidden
Visit us at : www.spsoftindia.com
On Fri, 2005-01-14 at 20:48, Chris Bergmann wrote:
> from my (limited) understanding of the vfs, this is not what you're
> looking for.
>
> I think vn_lock acts (as the name suggests) on a single vnode, not the
> whole filesystem. It won't suit your purposes if you're trying to lock
> out all writes to the entire volume.
>
> are you trying to add snapshots to HFS+ specifically, or just in a
> general way to all vfs file systems?
>
>
> On 15/01/2005, at 1:05, Yogesh P wrote:
>
> > Hi Folks,
> >
> > I am going through the implementation of the locking available in vfs
> > for holding the write call for fraction of time to initialize the
> > snapshot module.
> >
> > Can somebody point me about the vn_lock function which is used by lots
> > of syscall under bsd kernel.
> >
> > Can we directly use the vn_lock function to lock the write calls?
> >
> > Is there any reference document which will make me understand the
> > functionality of simple_lock,simple_unlock,VOP_LOCK and VOP_UNLOCK
> > under
> > darwin kernel.
> >
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden