public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suresh Jayaraman <sjayaraman@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Holger Kiehl <Holger.Kiehl@dwd.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-nfs@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: NFS write OOPS with 2.6.29.2
Date: Wed, 13 May 2009 16:20:02 +0530	[thread overview]
Message-ID: <4A0AA5DA.6090705@suse.de> (raw)
In-Reply-To: <1242046675.6691.6.camel@heimdal.trondhjem.org>

Trond Myklebust wrote:
> On Mon, 2009-05-11 at 12:45 +0000, Holger Kiehl wrote:
>> On Mon, 11 May 2009, Trond Myklebust wrote:
>>>
>> Thanks! Now it works. One more problem I have is with splice(). My
>> application reports the following error:
>>
>>     splice() error : Invalid argument
>>
>> When it is called as follows:
>>
>>      if ((bytes_written = splice(fd_pipe[0], NULL, to_fd,
>>                                  NULL, bytes_read,
>>                                  SPLICE_F_MOVE | SPLICE_F_MORE)) == -1)
>>
>> Or may I not use splice() over NFS?
> 
> The read part is there, but the write part is still missing (just an
> oversight - implementing it is pretty trivial). I'm planning on fixing
> that for 2.6.31.
> 

Did my latest respun look OK?

http://lkml.org/lkml/2009/4/22/70


Thanks,

-- 
Suresh Jayaraman

      reply	other threads:[~2009-05-13 10:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-03 16:03 NFS write OOPS with 2.6.29.2 Holger Kiehl
2009-05-05  6:14 ` Andrew Morton
2009-05-09 19:16   ` Holger Kiehl
2009-05-10  4:17     ` Trond Myklebust
2009-05-11  9:24       ` Holger Kiehl
2009-05-11 12:16         ` Trond Myklebust
2009-05-11 12:45           ` Holger Kiehl
2009-05-11 12:57             ` Trond Myklebust
2009-05-13 10:50               ` Suresh Jayaraman [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=4A0AA5DA.6090705@suse.de \
    --to=sjayaraman@suse.de \
    --cc=Holger.Kiehl@dwd.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox