1. 10 10月, 2007 10 次提交
  2. 11 7月, 2007 4 次提交
  3. 01 5月, 2007 1 次提交
  4. 15 2月, 2007 4 次提交
  5. 04 2月, 2007 1 次提交
  6. 08 12月, 2006 1 次提交
  7. 06 12月, 2006 14 次提交
  8. 22 11月, 2006 2 次提交
    • D
      WorkStruct: Pass the work_struct pointer instead of context data · 65f27f38
      David Howells 提交于
      Pass the work_struct pointer to the work function rather than context data.
      The work function can use container_of() to work out the data.
      
      For the cases where the container of the work_struct may go away the moment the
      pending bit is cleared, it is made possible to defer the release of the
      structure by deferring the clearing of the pending bit.
      
      To make this work, an extra flag is introduced into the management side of the
      work_struct.  This governs auto-release of the structure upon execution.
      
      Ordinarily, the work queue executor would release the work_struct for further
      scheduling or deallocation by clearing the pending bit prior to jumping to the
      work function.  This means that, unless the driver makes some guarantee itself
      that the work_struct won't go away, the work function may not access anything
      else in the work_struct or its container lest they be deallocated..  This is a
      problem if the auxiliary data is taken away (as done by the last patch).
      
      However, if the pending bit is *not* cleared before jumping to the work
      function, then the work function *may* access the work_struct and its container
      with no problems.  But then the work function must itself release the
      work_struct by calling work_release().
      
      In most cases, automatic release is fine, so this is the default.  Special
      initiators exist for the non-auto-release case (ending in _NAR).
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      65f27f38
    • D
      WorkStruct: Separate delayable and non-delayable events. · 52bad64d
      David Howells 提交于
      Separate delayable work items from non-delayable work items be splitting them
      into a separate structure (delayed_work), which incorporates a work_struct and
      the timer_list removed from work_struct.
      
      The work_struct struct is huge, and this limits it's usefulness.  On a 64-bit
      architecture it's nearly 100 bytes in size.  This reduces that by half for the
      non-delayable type of event.
      Signed-Off-By: NDavid Howells <dhowells@redhat.com>
      52bad64d
  9. 21 10月, 2006 1 次提交
  10. 29 9月, 2006 1 次提交
  11. 23 9月, 2006 1 次提交
    • C
      SUNRPC: Eliminate xprt_create_proto and rpc_create_client · ff9aa5e5
      Chuck Lever 提交于
      The two function call API for creating a new RPC client is now obsolete.
      Remove it.
      
      Also, remove an unnecessary check to see whether the caller is capable of
      using privileged network services.  The kernel RPC client always uses a
      privileged ephemeral port by default; callers are responsible for checking
      the authority of users to make use of any RPC service, or for specifying
      that a nonprivileged port is acceptable.
      
      Test plan:
      Repeated runs of Connectathon locking suite.  Check network trace to ensure
      correctness of NLM requests and replies.
      Signed-off-by: NChuck Lever <chuck.lever@oracle.com>
      Signed-off-by: NTrond Myklebust <Trond.Myklebust@netapp.com>
      ff9aa5e5