From: Suresh Jayaraman <sjayaraman@novell.com>
To: Gerd Bavendiek <gerd.bavendiek@googlemail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Differences between 2.6.5 und 2.6.16: getattr with actimeo=0 and O_DIRECT
Date: Tue, 13 Nov 2007 16:19:08 +0530 [thread overview]
Message-ID: <47398124.6070708@novell.com> (raw)
In-Reply-To: <4739686E.8080501@googlemail.com>
Gerd Bavendiek wrote:
>
> analyzing performance issues with Oracle databases on an NFS client
> running on SLES9 SP3 and NetApp as NFS server, I found that in SLES9
> SP3 each write call is followed by an getattr. This is not the case
> with SLES10 SP1.
The changes between 2.6.5 and 2.6.16 are too many that it is not easy to
track down.
> I do
>
> dd if=/dev/zero of=/mnt/qqq oflag=direct bs=8k count=100000
>
> and using tcpdump (BTW, is there an easier way ?) I see with SLES9 SP3
> (i.e. 2.6.5-7.244) each single 8k write followed by an getattr (which
> comes at some cost).
I Would suggest trying the latest kernel update from Novell/SUSE.
If the issue is seen in the latest kernels, create a bug report in
Novell/SUSE bugzilla - https://bugzilla.novell.com
Thanks,
--
Suresh Jayaraman
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-11-13 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-13 9:03 Differences between 2.6.5 und 2.6.16: getattr with actimeo=0 and O_DIRECT Gerd Bavendiek
2007-11-13 10:49 ` Suresh Jayaraman [this message]
2007-11-13 13:29 ` Trond Myklebust
2007-11-13 15:55 ` Gerd Bavendiek
2007-11-13 16:09 ` Chuck Lever
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=47398124.6070708@novell.com \
--to=sjayaraman@novell.com \
--cc=gerd.bavendiek@googlemail.com \
--cc=nfs@lists.sourceforge.net \
/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