From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: KELEMEN Peter <fuji@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS performance ...
Date: 28 Nov 2002 17:40:30 +0100 [thread overview]
Message-ID: <shs65uh1wch.fsf@charged.uio.no> (raw)
In-Reply-To: <20021128110627.GD26875@chiara.elte.hu>
>>>>> " " == KELEMEN Peter <fuji@elte.hu> writes:
> * Marc-Christian Petersen (m.c.p@wolk-project.de) [20021124
> 15:23]:
> Marc, Andrea,
>> I think Andrea and me have something in our kernels that may
>> cause it. For me I don't know what that can be. I even have no
>> idea what it can be :(
> The culprit turned out to be an inherited CONFIG_NFS_DIRECTIO
> setting. Having the client kernel (2.4.20rc2aa1) this option
> turned off, performance is stable 4 MB/sec (server hasn't
> changed). This is almost twice as good as with 2.4.19-rmap14b.
Huh? Sounds like something is seriously screwed up in your kernel
build then. CONFIG_NFS_DIRECTIO should should result in 2 things only:
- direct.c gets compiled.
- the 'direct_IO' address space operation gets defined, so that the
VFS knows what to do with files that get opened with the O_DIRECT
flag.
None of the ordinary NFS read and write code paths should be affected
by the above.
Cheers,
Trond
next prev parent reply other threads:[~2002-11-28 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-24 14:23 NFS performance Marc-Christian Petersen
2002-11-24 23:42 ` Andrea Arcangeli
2002-11-28 11:06 ` KELEMEN Peter
2002-11-28 16:40 ` Trond Myklebust [this message]
2002-11-28 21:36 ` KELEMEN Peter
2002-11-29 6:51 ` Trond Myklebust
2003-06-24 11:47 ` KELEMEN Peter
-- strict thread matches above, loose matches on Subject: below --
2002-11-22 15:00 KELEMEN Peter
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=shs65uh1wch.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=fuji@elte.hu \
--cc=linux-kernel@vger.kernel.org \
/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