Re: Why the RPC task structure adds a new field "tk_count"?

On Thu, 2006-04-27 at 14:32 -0400, Xin Zhao wrote:
> I migrate from 2.6.11 to 2.6.16, but found that a new field tk_count
> was added to the rpc task structure. In function rpc_release_task(), I
> saw the following code:
> 
> 	if (!atomic_dec_and_test(&task->tk_count))
> 		return;
> 
> 
> Looks like a task can be reused or refered multiple times? What's the
> theory behind this? Why do we need this?

It is used in several places in the NFSv4 code.

Cheers,
  Trond

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Why the RPC task structure adds a new field "tk_count"?
    • From: "Xin Zhao" <[email protected]>

• Prev by Date: Re: [RFC: 2.6 patch] fs/read_write.c: unexport iov_shorten
• Next by Date: RE: [(repost) git Patch 1/1] avoid IRQ0 ioapic pin collision
• Previous by thread: Why the RPC task structure adds a new field "tk_count"?
• Next by thread: [PATCH] NFS server subtree_check returns dubious value
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]