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

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?

Thanks,

Xin
-
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/

---

• Follow-Ups:
  • Re: Why the RPC task structure adds a new field "tk_count"?
    • From: Trond Myklebust <[email protected]>

• Prev by Date: Re: [PATCH 1/2] I386 fix pte clear
• Next by Date: Re: [RFC: 2.6 patch] fs/read_write.c: unexport iov_shorten
• Previous by thread: [2.6 patch] drivers/scsi/advansys.c: cleanups
• Next by thread: Re: Why the RPC task structure adds a new field "tk_count"?
• 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]