All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Yanling Song <songyl@ramaxel.com>
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] spraid: initial commit of Ramaxel spraid driver
Date: Tue, 19 Oct 2021 20:24:45 -0700	[thread overview]
Message-ID: <1abeda89-d7cf-9164-d8a1-3c764fd870a4@acm.org> (raw)
In-Reply-To: <20211020003323.61323f67@songyl>

On 10/19/21 17:33, Yanling Song wrote:
> On Wed, 13 Oct 2021 15:00:07 -0700
> Bart Van Assche <bvanassche@acm.org> wrote:
>> Please take a look at the bsg_setup_queue() call in ufs_bsg_probe().
>> That call associates a BSG queue with the UFS host. That queue
>> supports requests of type struct ufs_bsg_request. The Fibre Channel
>> transport driver does something similar. I believe that this is a
>> better solution than introducing entirely new ioctls.
> 
> I wish there was a standard way to address the ioctrl issue.
> Unfortunately ioctrl is the only way to meet our requirements as listed
> in the above.
> As discussed in previous megaraid's patchsets:
> https://lore.kernel.org/linux-scsi/yq1inc2y019.fsf@oracle.com/, that's
> why every raid controller has it's own ioctrl.

Why are ioctls the only solution? Why is a bsg interface attached to the 
SCSI host not appropriate? I haven't found the answer in the 
conversation about the Megaraid driver.

Thanks,

Bart.



  reply	other threads:[~2021-10-20  3:24 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-30  3:47 [PATCH] spraid: initial commit of Ramaxel spraid driver Yanling Song
2021-09-30  5:36 ` Randy Dunlap
2021-10-01  1:03   ` Yanling Song
2021-10-01  4:15 ` Christoph Hellwig
2021-10-08  9:22   ` Yanling Song
2021-10-09  3:58 ` Bart Van Assche
2021-10-09 13:32   ` Yanling Song
2021-10-10  3:52     ` Bart Van Assche
2021-10-11  8:34       ` Yanling Song
2021-10-11 19:40         ` Bart Van Assche
2021-10-12 11:10           ` Yanling Song
2021-10-11 19:54 ` Bart Van Assche
2021-10-12 14:49   ` Yanling Song
2021-10-12 16:59     ` Bart Van Assche
2021-10-13  6:50       ` Yanling Song
2021-10-13 22:00         ` Bart Van Assche
2021-10-15  5:48           ` Yanling Song
2021-10-20  0:33           ` Yanling Song
2021-10-20  3:24             ` Bart Van Assche [this message]
2021-11-03  1:43               ` Yanling Song
2021-11-05 13:02               ` Yanling Song
2021-11-05 16:13                 ` Bart Van Assche
2021-11-06  8:30                   ` Yanling Song

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=1abeda89-d7cf-9164-d8a1-3c764fd870a4@acm.org \
    --to=bvanassche@acm.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=songyl@ramaxel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.