linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Avri Altman <Avri.Altman@wdc.com>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH 0/4] ufs: Let the SCSI core allocate per-command UFS data
Date: Wed, 8 Jan 2020 14:53:13 -0800	[thread overview]
Message-ID: <d894ef4f-e506-74c1-4afd-5deb3437b6df@acm.org> (raw)
In-Reply-To: <MN2PR04MB699136BA44E4A11A606460E4FC3E0@MN2PR04MB6991.namprd04.prod.outlook.com>

On 1/8/20 5:14 AM, Avri Altman wrote:
> Aside of a mere simplification - is this change has other objectives?
> I am asking because at the end of the day not sure if using scsi privet data for the lrb is obtaining that goal.

Hi Avri,

Thanks for having taken a look. An important goal of this patch series 
is to optimize the UFS driver. This patch series should make the UFS 
driver slightly faster because it removes several pointer dereferences 
from the hot path and because it organizes all request-related data in a 
single contiguous address range.

Bart.


      reply	other threads:[~2020-01-08 22:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-07 19:25 [PATCH 0/4] ufs: Let the SCSI core allocate per-command UFS data Bart Van Assche
2020-01-07 19:25 ` [PATCH 1/4] Introduce {init,exit}_cmd_priv() Bart Van Assche
2020-01-07 19:25 ` [PATCH 2/4] ufs: Introduce ufshcd_init_lrb() Bart Van Assche
2020-01-09 10:28   ` Avri Altman
2020-01-19 14:38   ` Alim Akhtar
2020-01-07 19:25 ` [PATCH 3/4] ufs: Simplify two tests Bart Van Assche
2020-01-09 10:29   ` Avri Altman
2020-01-10 17:17   ` asutoshd
2020-01-11  7:21   ` Stanley Chu
2020-01-07 19:25 ` [PATCH 4/4] ufs: Let the SCSI core allocate per-command UFS data Bart Van Assche
2020-01-09  9:48   ` Avri Altman
2020-01-09 22:28     ` Bart Van Assche
2020-01-10 12:03       ` Avri Altman
2020-01-08 13:14 ` [PATCH 0/4] " Avri Altman
2020-01-08 22:53   ` Bart Van Assche [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=d894ef4f-e506-74c1-4afd-5deb3437b6df@acm.org \
    --to=bvanassche@acm.org \
    --cc=Avri.Altman@wdc.com \
    --cc=hch@lst.de \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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).