From: Tejun Heo <tj@kernel.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: linux-ide@vger.kernel.org, Jens Axboe <axboe@fb.com>,
Shaohua Li <shli@fb.com>, Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 2/2] libata: micro-optimize tag allocation
Date: Mon, 19 Jan 2015 09:14:48 -0500 [thread overview]
Message-ID: <20150119141448.GC8140@htj.dyndns.org> (raw)
In-Reply-To: <20150116231307.18771.52330.stgit@viggo.jf.intel.com>
On Fri, Jan 16, 2015 at 03:13:08PM -0800, Dan Williams wrote:
> Jens notes, "libata tag allocator sucks. Like seriously sucks, it's
> almost a worst case implementation." Previously I thought SATA mmio
> latency dominated performance profiles, but as Tejun notes:
>
> "Hmmm... one problem with the existing tag allocator in ata is that
> it's not very efficient which actually shows up in profile when libata
> is used with a very zippy SSD. Given that ata needs a different
> allocation policies anyway maybe the right thing to do is making the
> existing allocator suck less."
>
> So replace it with a naive enhancement that also supports the existing
> quirks. Hopefully, soon to be replaced by Shaohua's patches [1], but
> those do not yet support the quirk needed by sil24 (ATA_FLAG_LOWTAG)
> [2].
>
> [1]: http://marc.info/?l=linux-ide&m=142137195324687&w=2
> [2]: https://bugzilla.kernel.org/show_bug.cgi?id=87101
>
> Cc: Jens Axboe <axboe@fb.com>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Shaohua Li <shli@fb.com>
> Cc: Christoph Hellwig <hch@infradead.org>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Hmmm... if libata using blk-tag isn't ugly, I think that prolly is the
better way to proceed. Let's see how that develops.
Thanks.
--
tejun
prev parent reply other threads:[~2015-01-19 14:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 23:12 [PATCH 0/2] fix sil24 regression and muddy the ata tag allocation waters Dan Williams
2015-01-16 23:13 ` [PATCH 1/2] libata: allow sata_sil24 to opt-out of tag ordered submission Dan Williams
2015-01-17 10:59 ` Sergei Shtylyov
[not found] ` <CAPcyv4h3n+cnvADiEbGgi1EFCqEwhzZ7gt_6XUmSC62aOf2Dzw@mail.gmail.com>
2015-01-17 18:43 ` Sergei Shtylyov
2015-01-19 14:12 ` Tejun Heo
2015-01-19 14:24 ` Sergei Shtylyov
2015-01-19 14:27 ` Tejun Heo
2015-01-19 14:13 ` Tejun Heo
2015-01-16 23:13 ` [PATCH 2/2] libata: micro-optimize tag allocation Dan Williams
2015-01-16 23:17 ` Jens Axboe
2015-01-16 23:19 ` Dan Williams
2015-01-16 23:21 ` Jens Axboe
2015-01-16 23:38 ` Dan Williams
2015-01-16 23:31 ` Shaohua Li
2015-01-16 23:49 ` Dan Williams
2015-01-16 23:55 ` Shaohua Li
2015-01-16 23:59 ` Dan Williams
2015-01-17 0:10 ` Shaohua Li
2015-01-19 14:14 ` Tejun Heo [this message]
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=20150119141448.GC8140@htj.dyndns.org \
--to=tj@kernel.org \
--cc=axboe@fb.com \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=shli@fb.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;
as well as URLs for NNTP newsgroup(s).