From: Christoph Hellwig <hch@lst.de>
To: Tejun Heo <tj@kernel.org>
Cc: linux-ide@vger.kernel.org, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org
Subject: Re: command emulation fix
Date: Thu, 19 Jan 2017 21:40:16 +0100 [thread overview]
Message-ID: <20170119204016.GA6610@lst.de> (raw)
In-Reply-To: <20170119203458.GC25390@mtj.duckdns.org>
On Thu, Jan 19, 2017 at 03:34:58PM -0500, Tejun Heo wrote:
> So, unless we allocate one mempool per port, we're gonna have to
> synchronize around its use anyway. mempool can't guarantee allocation
> to multiple users at the same time. If this is something which
> affects scalability, I'm completley fine with making it per-port (or
> device). Each ata_port carries 512 byte buffer anyway. Maybe we can
> reuse that?
I'll play around with these things a bit more. For the slow
path ops I think I can get away without any dynamic allocation
at all - just use small on-stack buffers.
For DSM / Write Same we rewrite into the buffer the SCSI layer
provided us. This is a bit of an issue anyway as this might
modify user data that is not expected to be rewritten or even
mapped read-only. Maybe we need to kill off that emulation
entirely and just have ATA DSM using the ATA_16 CDB as another
provisioning option in sd.c. While that is a bit of a layering
violation it would solve a lot of problems with the way TRIM
is currently implemented.
prev parent reply other threads:[~2017-01-19 20:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-14 16:50 command emulation fix Christoph Hellwig
2017-01-14 16:50 ` [PATCH] libata: switch allocations for command emulation to GFP_ATOMIC Christoph Hellwig
2017-01-15 23:07 ` command emulation fix Tejun Heo
2017-01-16 15:21 ` Christoph Hellwig
2017-01-18 19:17 ` Tejun Heo
2017-01-19 14:35 ` Christoph Hellwig
2017-01-19 20:23 ` Tejun Heo
2017-01-19 20:27 ` Christoph Hellwig
2017-01-19 20:34 ` Tejun Heo
2017-01-19 20:36 ` Tejun Heo
2017-01-19 20:41 ` Christoph Hellwig
2017-01-19 20:45 ` Tejun Heo
2017-01-19 20:40 ` Christoph Hellwig [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=20170119204016.GA6610@lst.de \
--to=hch@lst.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tj@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).