All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas D <nd@saitis.net>
To: target-devel@vger.kernel.org
Subject: Re: MaxTransferLength
Date: Wed, 13 Jun 2018 11:31:15 +0000	[thread overview]
Message-ID: <20180613113115.GA22509@hydro.skol.ch> (raw)
In-Reply-To: <20180424122512.GQ27687@hydro.skol.ch>


Hello,

On Thu, May 24, 2018 at 08:46:46AM -0500, Bryant G. Ly wrote:
> 
> The use of user:fbo is to emulate an optical device... So you would
> want to map an ISO9660 filesystem.
> 
> In this case you would do:
> 
> sudo targetcli /backstores/user:fbo create name=test_name
> cfgstring=/home/test/path.iso size\x10000
> 
> Then you would map this backstore device to a fabric lun. Afterwards,
> on the client VM you would see this as dev/sr0 when you boot up.

So I won't be able to solve my problem at all. I just read again what I
wrote in this thread and I think I was clear enough, tell me if I am
wrong. In my use case:

- Optical media (CD, DVD, BluRay) have to be served directly
- All commands related to optical drive authentication should be
  supported (and it works well with pscsi), it is needed to play
  protected content.

I still don't understand why this problenm can't be solved easily. AFAIK
maxtransferlength is negociated on login and seems to be
MIN(initiator,target)

Also, tell me if you think there's a better place to ask for help about
this case.

Nicolas

      parent reply	other threads:[~2018-06-13 11:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-24 12:25 MaxTransferLength Nicolas D
2018-04-24 12:38 ` MaxTransferLength Hannes Reinecke
2018-04-24 12:53 ` MaxTransferLength Bryant G. Ly
2018-04-25 10:13 ` MaxTransferLength Nicolas D
2018-04-25 13:46 ` MaxTransferLength Bryant G. Ly
2018-05-23 20:48 ` MaxTransferLength Nicolas D
2018-05-24 13:46 ` MaxTransferLength Bryant G. Ly
2018-06-13 11:31 ` Nicolas D [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=20180613113115.GA22509@hydro.skol.ch \
    --to=nd@saitis.net \
    --cc=target-devel@vger.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 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.