public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: james harvey <jamespharvey20-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [QUESTION] Is an ib_sbft kernel module needed to be made? (For booting using SRP)
Date: Tue, 19 Jul 2016 12:18:39 +0300	[thread overview]
Message-ID: <20160719091838.GI20674@leon.nu> (raw)
In-Reply-To: <CA+X5Wn4aYpxAKO5aCQS+T1MH1MMedd+ukBecZGSbg02QdX1YSQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

On Mon, Jul 18, 2016 at 10:13:15PM -0400, james harvey wrote:
> I'm looking to boot using SRP.  I've spent a lot of time looking, and
> am not seeing that anyone has actually done this.  Really surprises
> me, actually.
> 
> iPXE is able to make the SRP connection, load the kernel and
> initramfs, and leaves behind a SRP boot firmware table as described at
> http://ipxe.org/srp/sbft
> 
> But, I don't see anything that finds, reads, or uses it.  So then then
> remote drive is no longer seen.
> 
> I see iSCSI handles this problem through the kernel module iscsi_ibft
> which gives a sysfs interface to iSCSI's BFT structure.
> 
> I'm somewhat interested in developing the ib_sbft kernel module, if
> I'm not missing an existing alternative to allow SRP booting.  I
> expect I could work from the iscsi_ibft kernel module source to be
> able to accomplish this, making the necessary changes based on the
> sBFT documentation and iPXE's sBFT-creating source.
> 
> Is anyone else who has done kernel development interested in taking
> that on, or is it something I should start working on?
> 

Is this ability needed? Do you have real life scenario for this?

Thanks

> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2016-07-19  9:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19  2:13 [QUESTION] Is an ib_sbft kernel module needed to be made? (For booting using SRP) james harvey
     [not found] ` <CA+X5Wn4aYpxAKO5aCQS+T1MH1MMedd+ukBecZGSbg02QdX1YSQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-07-19  9:18   ` Leon Romanovsky [this message]
2016-07-19 16:46   ` 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=20160719091838.GI20674@leon.nu \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=jamespharvey20-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.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