public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Christie <michaelc@cs.wisc.edu>
To: Mike Christie <michaelc@cs.wisc.edu>
Cc: dougg@torque.net, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/2] convert sg to blk_rq map functions
Date: Mon, 15 Aug 2005 15:06:27 -0500	[thread overview]
Message-ID: <4300F5C3.1080006@cs.wisc.edu> (raw)
In-Reply-To: <4300F49C.3000404@cs.wisc.edu>

Mike Christie wrote:
> 
> Block layer defines the max segment size as 65536. We need
> new block layer helpers to do the mapping. Although one late night
> I thought I could use a modified blk_rq_map_kern some how. If sg or
> st allocate the reserve buffers then we could make a

oops, I meant sg or st would allocate the reserves or huge
buffers/pages/segments using some block layer helper becuase the
block layer knows the segment and size limits a little better. But
the sg or st driver would pass in the reserves to the block layer
mapping function similar to how we can pass in bio_sets to the bio code.

> blk_rq_map_kern_iovec function that worked similar to its
> user cousin but of course operated on a iovec of kernel buffers.
> But then I am not sure if at that point we should just be
> interacting with the bio code directly instead of adding a
> extra iovec abstraction. I would guess for SCSI drivers at least
> it is nicer to not worry about bio internals though. James
> and Jens would konw best though.
> 
> 

      reply	other threads:[~2005-08-15 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-09  4:38 [PATCH 2/2] convert sg to blk_rq map functions Mike Christie
2005-08-15 12:29 ` Douglas Gilbert
2005-08-15 20:01   ` Mike Christie
2005-08-15 20:06     ` Mike Christie [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=4300F5C3.1080006@cs.wisc.edu \
    --to=michaelc@cs.wisc.edu \
    --cc=dougg@torque.net \
    --cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox