linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Steve French" <smfrench@gmail.com>
To: "Evgeniy Polyakov" <johnpol@2ka.mipt.ru>
Cc: "Jeff Layton" <jlayton@redhat.com>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	"Shirish Pargaonkar" <shirishpargaonkar@gmail.com>,
	"Dave Kleikamp" <shaggy@linux.vnet.ibm.com>
Subject: Re: flush and EIO errors when writepages fails
Date: Sat, 21 Jun 2008 12:02:31 -0500	[thread overview]
Message-ID: <524f69650806211002s3eb211fbs407e18cdb51a94b7@mail.gmail.com> (raw)
In-Reply-To: <20080621162825.GA11100@2ka.mipt.ru>

On Sat, Jun 21, 2008 at 11:28 AM, Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> You can also hack into socket code like tcp_sendmsg()/tcp_sendpage()
> (the latter is not used in CIFS though)

Your point about tcp_sendpage reminds me of something I have been wondering
about for a while.  Since SunRPC switched to kernel_sendpage I have
been wondering
whether that is better or worse than kernel_sendmsg.   It looks like
in some cases
sendpage simply falls back to calling sendmsg with 1 iovec (instead of calling
tcp_sendpage which calls do_tcp_sendpages) which would end up being
slower than calling
sendmsg with a larger iovec as we do in smb_send2 in the write path.

For the write case in which we are writing pages (that are aligned)
out of the page cache to
the socket would sendpage be any faster than sendmsg?  (I wish there
was a sendmultiple
pages call where I could pass the whole list of pages).  How should a
piece of kernel
code check to see if sendpage is supported/faster and when to use
kernel_sendpage and
when to use sendmsg with the pages in the iovec

-- 
Thanks,

Steve

  reply	other threads:[~2008-06-21 17:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-20 22:34 flush and EIO errors when writepages fails Steve French
2008-06-21  7:05 ` Evgeniy Polyakov
2008-06-21 12:27   ` Jeff Layton
2008-06-21 13:19     ` Evgeniy Polyakov
2008-06-21 14:21       ` Jody French
2008-06-21 14:42         ` Evgeniy Polyakov
2008-06-21 16:15           ` Steve French
2008-06-21 16:28             ` Evgeniy Polyakov
2008-06-21 17:02               ` Steve French [this message]
2008-06-21 17:26                 ` Evgeniy Polyakov
2008-06-21 17:37                   ` Evgeniy Polyakov
2008-06-23 15:39         ` Dave Kleikamp
2008-06-23 18:05           ` Dave Kleikamp
     [not found] <20080620073150.2bc9988e@tupile.poochiereds.net>
     [not found] ` <OFE8C66E61.981E25D1-ON8725746E.0045A92A-8625746E.004718C0@us.ibm.com>
     [not found]   ` <20080620091542.09edb43f@tupile.poochiereds.net>
2008-06-20 16:19     ` Steve French (smfltc)
2008-06-20 16:34       ` Jeff Layton
2008-06-20 16:41         ` Steve French (smfltc)
2008-06-20 17:12           ` Jeff Layton

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=524f69650806211002s3eb211fbs407e18cdb51a94b7@mail.gmail.com \
    --to=smfrench@gmail.com \
    --cc=jlayton@redhat.com \
    --cc=johnpol@2ka.mipt.ru \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=shaggy@linux.vnet.ibm.com \
    --cc=shirishpargaonkar@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).