Filesystems might have some blocksize and alignment constraints
conditioning their ability to loan up buffers (for writes).
If that is so, we could use an API to query the FS about
those values. For a copy on write variable block size
filesystem, that natural blocksize might also depend on the
Are there instances where an assigned zero-copy buffer could be orphaned?
If so, should there be a recovery list associated with this addition?
Perhaps off
the designated vnode.
This comment shouldn't block fast-track approval. Just a question.
--
Rick
On 09/ 9/09 04:02 PM, Rich.Brown at
Roch wrote:
Filesystems might have some blocksize and alignment constraints
conditioning their ability to loan up buffers (for writes).
If that is so, we could use an API to query the FS about
those values. For a copy on write variable block size
filesystem, that natural blocksize might
Rick Matthews wrote:
Are there instances where an assigned zero-copy buffer could be orphaned?
No. The consumer Must release the buffers through VOP_RETZCBUF().
Mahesh
If so, should there be a recovery list associated with this addition?
Perhaps off
the designated vnode.
This comment
My issues have been resolved. Thanks Mahesh.
-r
Rich.Brown at Sun.COM writes:
I'm sponsoring this case on behalf of Mahesh Siddheshwar and Chunli Zhang.
This case proposes new interfaces to support copy reduction in the I/O path
especially for file sharing services.
Minor binding is
This case was approved at today's PSARC meeting.
I put an updated final_spec.txt in the case directory
which corrects a typo that Mahesh found.
On behalf of the team, thank you for your time and assistance
on this case.
Rich
On Wed, Sep 09, 2009 at 04:02:15PM -0500, Rich.Brown at sun.com wrote:
== Introduction/Background ==
Zero-copy (copy avoidance) is essentially buffer sharing
among multiple modules that pass data between the modules.
This proposal avoids the data copy in the READ/WRITE path
of
johansen at sun.com wrote:
On Wed, Sep 09, 2009 at 04:02:15PM -0500, Rich.Brown at sun.com wrote:
== Introduction/Background ==
Zero-copy (copy avoidance) is essentially buffer sharing
among multiple modules that pass data between the modules.
This proposal avoids the data copy in
On 09/09/09 17:08, Garrett D'Amore wrote:
I've not had time to go over all this yet, but do we really believe this
kind of change is fast track appropriate? I have a feeling that this is
a significant enough core change with implications for a variety of
project teams, that maybe this one
I'm sponsoring this case on behalf of Mahesh Siddheshwar and Chunli Zhang.
This case proposes new interfaces to support copy reduction in the I/O path
especially for file sharing services.
Minor binding is requested.
This times out on Wednesday, 16 September, 2009.
Template Version:
I've not had time to go over all this yet, but do we really believe this
kind of change is fast track appropriate? I have a feeling that this is
a significant enough core change with implications for a variety of
project teams, that maybe this one ought to be a full case. I'd be a
bit
Garrett D'Amore wrote:
I've not had time to go over all this yet, but do we really believe
this kind of change is fast track appropriate? I have a feeling that
this is a significant enough core change with implications for a
variety of project teams, that maybe this one ought to be a full
12 matches
Mail list logo
