public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Emmanuel Florac <eflorac@intellique.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Michael Monnerie <michael.monnerie@is.it-management.at>, xfs@oss.sgi.com
Subject: Re: Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1
Date: Wed, 27 Oct 2010 12:06:28 +0200	[thread overview]
Message-ID: <20101027120628.7b4b2e20@harpe.intellique.com> (raw)
In-Reply-To: <4CC7CDF6.3080405@profihost.ag>

Le Wed, 27 Oct 2010 09:00:06 +0200
Stefan Priebe - Profihost AG <s.priebe@profihost.ag> écrivait:

> So what values do you recommand in general for iSCSI on Serverside
> and which values on iSCSI client side?
> 

Depends upon the hardware. nr_requests should be 512 for 3Ware cards,
256 to 1024 for other controllers (always more than the default 128
anyway). 

Same rule goes for read-ahead; however many RAID controllers (Areca,
Adaptec) "cheat" and do read-ahead optimisation by themselves (which
may harm random access). The default read-ahead value (256) was OK for
obsolete ATA drives with a few KB of cache; nowadays all drives have 32
or 64 MB, and controllers 512 MB to several GB, so more read-ahead can
do no harm but fill the cache up. I often go up to 65536 or 131072
sectors (for 24 or 48 drives arrays). Keep in mind that this is
sequentail-raid optimisation; random access (such as VM work) may give
better result with lower read-ahead values. Benchmarking your
application is king here.

Just for information : I currently run some servers with kernel
2.6.22.18 (march 2008) and 3Ware firmware 4.10.0.7, so upgrading your
2.6.23 system should be perfectly safe from a driver compatibility
point of view.

-- 
------------------------------------------------------------------------
Emmanuel Florac     |   Direction technique
                    |   Intellique
                    |	<eflorac@intellique.com>
                    |   +33 1 78 94 84 02
------------------------------------------------------------------------

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-10-27 10:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  6:25 Pid: 8345, comm: rsync Not tainted 2.6.32.22intel #1 Stefan Priebe - Profihost AG
2010-10-26  7:22 ` Emmanuel Florac
2010-10-26  7:24   ` Stefan Priebe - Profihost AG
2010-10-26  7:41     ` Emmanuel Florac
2010-10-26  7:53       ` Stefan Priebe - Profihost AG
2010-10-26 11:01         ` Emmanuel Florac
2010-10-26 11:03           ` Stefan Priebe - Profihost AG
2010-10-26 11:25             ` Emmanuel Florac
2010-10-26 12:09               ` Stefan Priebe - Profihost AG
2010-10-26 13:00                 ` Emmanuel Florac
2010-10-26 23:23               ` Michael Monnerie
2010-10-27  3:55                 ` Dave Chinner
2010-10-27 10:58                   ` Michael Monnerie
2010-10-27 20:59                     ` Dave Chinner
2010-10-28  9:39                       ` Michael Monnerie
2010-10-27  6:04                 ` Emmanuel Florac
2010-10-27  7:00                   ` Stefan Priebe - Profihost AG
2010-10-27 10:06                     ` Emmanuel Florac [this message]
2010-10-27 10:08                       ` Stefan Priebe - Profihost AG
2010-10-27 10:12                         ` Emmanuel Florac
2010-10-27 10:22                           ` Stefan Priebe - Profihost AG
2010-10-27 11:14                             ` Emmanuel Florac
2010-10-26 11:30             ` Larsen, Tore Høivaag
2010-10-26 11:47               ` Emmanuel Florac
2010-11-01  8:01     ` Stefan Priebe - Profihost AG
2010-11-01 10:11       ` Emmanuel Florac
2010-11-01 10:28         ` Stefan Priebe - Profihost AG
2010-11-01 12:27       ` Dave Chinner
2010-11-01 12:28         ` Stefan Priebe - Profihost AG
2010-11-01 12:52           ` Dave Chinner
2010-11-01 13:29           ` Emmanuel Florac
2010-11-01 13:48             ` Stefan Priebe - Profihost AG

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=20101027120628.7b4b2e20@harpe.intellique.com \
    --to=eflorac@intellique.com \
    --cc=michael.monnerie@is.it-management.at \
    --cc=s.priebe@profihost.ag \
    --cc=xfs@oss.sgi.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