From: Jens Axboe <axboe@suse.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: libata: clustering on or off?
Date: Sun, 28 Aug 2005 16:20:19 +0200 [thread overview]
Message-ID: <20050828142018.GS4018@suse.de> (raw)
In-Reply-To: <1125224541.3219.13.camel@laptopd505.fenrus.org>
On Sun, Aug 28 2005, Arjan van de Ven wrote:
> On Sun, 2005-08-28 at 05:42 -0400, Jeff Garzik wrote:
> > 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?
>
> in 2.4 clustering was expensive due to a large number of checks that
> were done (basically the number of fragments got recounted a gazilion
> times). In 2.6 Jens fixed that afaik to make it basically free...
> at which point it's a win always.
Yeah, it wont cost any extra cycles, so there's no point in keeping it
turned off for that reason.
> Imo clustering on the driver level should announce driver capabilities.
> If clustering for some arch/kernel makes it slower, that should be
> decided at a midlayer level and not in each driver; eg the midlayer
> would chose to ignore the drivers capabilities.
> So .. my opinion would be that libata should announce the capability (it
> seems the code/hw can do it).
Agree, we should just remove the ability to control clustering, as it
really overlaps with the segment settings anyways.
--
Jens Axboe
next prev parent reply other threads:[~2005-08-28 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 9:42 libata: clustering on or off? Jeff Garzik
2005-08-28 10:22 ` Arjan van de Ven
2005-08-28 14:20 ` Jens Axboe [this message]
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=20050828142018.GS4018@suse.de \
--to=axboe@suse.de \
--cc=arjan@infradead.org \
--cc=jgarzik@pobox.com \
--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).