From: Jeff Garzik <jgarzik@pobox.com>
To: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Cc: axboe@suse.de
Subject: libata: clustering on or off?
Date: Sun, 28 Aug 2005 05:42:18 -0400 [thread overview]
Message-ID: <20050828094218.GA29145@havoc.gtf.org> (raw)
The constant ATA_SHT_USE_CLUSTERING in include/linux/libata.h controls
the use of SCSI layer's use_clustering feature, for a great many libata
drivers.
The current setup has clustering disabled, which in theory causes the
block layer to do less work, at the expense of a greater number of
scatter/gather table entries used.
Any opinions WRT turning on clustering for libata?
Jeff
next reply other threads:[~2005-08-28 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 9:42 Jeff Garzik [this message]
2005-08-28 10:22 ` libata: clustering on or off? Arjan van de Ven
2005-08-28 14:20 ` Jens Axboe
2005-08-28 14:58 ` Christoph Hellwig
2005-08-28 15:09 ` Jens Axboe
2005-08-28 17:32 ` Jeff Garzik
2005-08-28 18:01 ` Jens Axboe
2005-08-29 15:56 ` Mark Lord
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=20050828094218.GA29145@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=axboe@suse.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).