All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tao Ma <tao.ma@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 4/4] ocfs2-1.6: add splice read/write support
Date: Mon, 15 Mar 2010 14:32:25 +0800	[thread overview]
Message-ID: <4B9DD479.3050100@oracle.com> (raw)
In-Reply-To: <4B9DCF36.3020906@oracle.com>



Tiger Yang wrote:
> Tao Ma wrote:
>>> +void pipe_wait(struct pipe_inode_info *pipe)
>> I just see that el5 already has splice support, see 
>> http://www.redhat.com/rhel/features/
>>
>> So we still need to copy these functions back? At least in el5u2, I 
>> see these functions like pipe_wait, pipe_to_file etc.
> 
> Yes. We need copy these functions because they are not exported by the 
> kernel of el5.
> 
> Because the struct splice_desc has been changed since 2.6.30, it it 
> difficult to back port the latest code in mainline. So I chose the 
> splice code in 2.6.29 for back porting. I hope the latest code before 
> change are more stable and efficient.
oh, I see. I just checked the source code in 1.4. Thanks for the 
explanation.

Regards,
Tao

      reply	other threads:[~2010-03-15  6:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-12  9:05 [Ocfs2-devel] [PATCH 1/4] ocfs2-1.6: pipe operation pin() changes to confirm() Tiger Yang
2010-03-12  9:07 ` [Ocfs2-devel] [PATCH 2/4] ocfs2-1.6: Add inode_double_lock()/unlock() Tiger Yang
2010-03-12  9:07 ` [Ocfs2-devel] [PATCH 3/4] ocfs2-1.6: Add file_remove_suid() Tiger Yang
2010-03-12  9:07 ` [Ocfs2-devel] [PATCH 4/4] ocfs2-1.6: add splice read/write support Tiger Yang
2010-03-12  9:19   ` Tao Ma
2010-03-15  6:09     ` Tiger Yang
2010-03-15  6:32       ` Tao Ma [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B9DD479.3050100@oracle.com \
    --to=tao.ma@oracle.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.