From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: NeilBrown <neilb@suse.de>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org,
"Vladimir V \".\" Saveliev" <vs@namesys.com>,
Norman Weathers <norman.r.weathers@conocophillips.com>
Subject: Re: [PATCH] knfsd: Stop NFSD writes from being broken into lots of little writes to filesystem.
Date: Wed, 14 Feb 2007 13:44:08 -0800 [thread overview]
Message-ID: <20070214134408.431cddcc.akpm@linux-foundation.org> (raw)
In-Reply-To: <45D15687.5080505@yahoo.com.au>
On Tue, 13 Feb 2007 17:11:19 +1100
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> NeilBrown wrote:
> > Another nfsd patch for 2.6.21...
> >
> > ### Comments for Changeset
> >
> > When NFSD receives a write request, the data is typically in a number
> > of 1448 byte segments and writev is used to collect them together.
> >
> > Unfortunately, generic_file_buffered_write passes these to the filesystem
> > one at a time, so an e.g. 32K over-write becomes a series of partial-page
> > writes to each page, causing the filesystem to have to pre-read those
> > pages - wasted effort.
> >
> > generic_file_buffered_write handles one segment of the vector at a
> > time as it has to pre-fault in each segment to avoid deadlocks. When
> > writing from kernel-space (and nfsd does) this is not an issue, so
> > generic_file_buffered_write does not need to break and iovec from nfsd
> > into little pieces.
> >
> > This patch avoids the splitting when get_fs is KERNEL_DS as it is
> > from NFSd.
> >
> > This issue was introduced by commit 6527c2bdf1f833cc18e8f42bd97973d583e4aa83
> >
> > Cc: Nick Piggin <nickpiggin@yahoo.com.au>
>
> FWIW, you can put Acked-by: me there if you'd like.
>
It's yet another patch we need to revert if/when we get the write()-deadlock
stuff sorted out. So please add negative-this to that patch series.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: NeilBrown <neilb@suse.de>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org,
Norman Weathers <norman.r.weathers@conocophillips.com>,
"Vladimir V \".\" Saveliev" <vs@namesys.com>
Subject: Re: [PATCH] knfsd: Stop NFSD writes from being broken into lots of little writes to filesystem.
Date: Wed, 14 Feb 2007 13:44:08 -0800 [thread overview]
Message-ID: <20070214134408.431cddcc.akpm@linux-foundation.org> (raw)
In-Reply-To: <45D15687.5080505@yahoo.com.au>
On Tue, 13 Feb 2007 17:11:19 +1100
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> NeilBrown wrote:
> > Another nfsd patch for 2.6.21...
> >
> > ### Comments for Changeset
> >
> > When NFSD receives a write request, the data is typically in a number
> > of 1448 byte segments and writev is used to collect them together.
> >
> > Unfortunately, generic_file_buffered_write passes these to the filesystem
> > one at a time, so an e.g. 32K over-write becomes a series of partial-page
> > writes to each page, causing the filesystem to have to pre-read those
> > pages - wasted effort.
> >
> > generic_file_buffered_write handles one segment of the vector at a
> > time as it has to pre-fault in each segment to avoid deadlocks. When
> > writing from kernel-space (and nfsd does) this is not an issue, so
> > generic_file_buffered_write does not need to break and iovec from nfsd
> > into little pieces.
> >
> > This patch avoids the splitting when get_fs is KERNEL_DS as it is
> > from NFSd.
> >
> > This issue was introduced by commit 6527c2bdf1f833cc18e8f42bd97973d583e4aa83
> >
> > Cc: Nick Piggin <nickpiggin@yahoo.com.au>
>
> FWIW, you can put Acked-by: me there if you'd like.
>
It's yet another patch we need to revert if/when we get the write()-deadlock
stuff sorted out. So please add negative-this to that patch series.
next prev parent reply other threads:[~2007-02-14 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070213170049.3488.patches@notabene>
2007-02-13 6:01 ` [PATCH] knfsd: Stop NFSD writes from being broken into lots of little writes to filesystem NeilBrown
2007-02-13 6:01 ` NeilBrown
2007-02-13 6:11 ` Nick Piggin
2007-02-13 6:11 ` Nick Piggin
2007-02-14 21:44 ` Andrew Morton [this message]
2007-02-14 21:44 ` Andrew Morton
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=20070214134408.431cddcc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=nickpiggin@yahoo.com.au \
--cc=norman.r.weathers@conocophillips.com \
--cc=vs@namesys.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.