public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K . Petersen" <martin.petersen@oracle.com>,
	"James E . J . Bottomley" <jejb@linux.vnet.ibm.com>
Cc: linux-scsi@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH 0/4] Simplify and optimize the UFS driver
Date: Thu, 31 Oct 2019 15:55:24 -0700	[thread overview]
Message-ID: <20191031225528.233895-1-bvanassche@acm.org> (raw)

Hi Martin,

While reading the UFS source code I noticed that some existing mechanisms
are duplicated in this driver. These patches simplify and optimize the UFS
driver. These patches are entirely untested.

Bart.

Bart Van Assche (4):
  ufs: Avoid busy-waiting by eliminating tag conflicts
  ufs: Simplify the clock scaling mechanism implementation
  ufs: Remove the SCSI timeout handler
  ufs: Remove superfluous memory barriers

 drivers/scsi/ufs/ufshcd.c | 288 +++++++++++---------------------------
 drivers/scsi/ufs/ufshcd.h |  12 +-
 2 files changed, 90 insertions(+), 210 deletions(-)

             reply	other threads:[~2019-10-31 22:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31 22:55 Bart Van Assche [this message]
2019-10-31 22:55 ` [PATCH 1/4] ufs: Avoid busy-waiting by eliminating tag conflicts Bart Van Assche
2019-10-31 22:55 ` [PATCH 2/4] ufs: Simplify the clock scaling mechanism implementation Bart Van Assche
2019-10-31 22:55 ` [PATCH 3/4] ufs: Remove the SCSI timeout handler Bart Van Assche
2019-10-31 22:55 ` [PATCH 4/4] ufs: Remove superfluous memory barriers Bart Van Assche
2019-11-04 14:34 ` [PATCH 0/4] Simplify and optimize the UFS driver Avri Altman
2019-11-04 15:55   ` Bart Van Assche

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=20191031225528.233895-1-bvanassche@acm.org \
    --to=bvanassche@acm.org \
    --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