From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: Kevin Wolf <kwolf@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Hannes Reinecke <hare@suse.de>,
ronnie sahlberg <ronniesahlberg@gmail.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] scsi-generic and max request size
Date: Thu, 23 Dec 2010 10:44:17 +1100 [thread overview]
Message-ID: <1293061457.16694.791.camel@pasglop> (raw)
In-Reply-To: <38550122-4CCE-4F97-BCA3-4AA37230D623@suse.de>
On Thu, 2010-12-23 at 00:39 +0100, Alexander Graf wrote:
> This all belongs in the block layer. If you create a call back
> function or property in the block struct, windows can implement its
> own limits when someone sits down to implement SG_IO on Windows.
Right and we do have "generic" ways it seems to interrogate those
limits .. except they seem to be broken for "sg" :-)
Also I've spotted some oddities where the ioctl for the max request size
sometimes put_user as a int * and sometimes as a short * ... ooops...
Cheers,
Ben.
next prev parent reply other threads:[~2010-12-22 23:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 3:25 [Qemu-devel] scsi-generic and max request size Benjamin Herrenschmidt
2010-12-21 3:38 ` ronnie sahlberg
2010-12-21 3:52 ` Benjamin Herrenschmidt
2010-12-21 8:44 ` Hannes Reinecke
2010-12-21 22:05 ` Benjamin Herrenschmidt
2010-12-22 13:54 ` Hannes Reinecke
2010-12-22 13:27 ` Christoph Hellwig
2010-12-22 22:06 ` Benjamin Herrenschmidt
2010-12-22 23:19 ` Alexander Graf
2010-12-22 21:59 ` Benjamin Herrenschmidt
2010-12-22 23:23 ` Alexander Graf
2010-12-22 23:35 ` Benjamin Herrenschmidt
2010-12-22 23:39 ` Alexander Graf
2010-12-22 23:44 ` Benjamin Herrenschmidt [this message]
2010-12-22 23:49 ` Alexander Graf
2010-12-23 0:00 ` Benjamin Herrenschmidt
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=1293061457.16694.791.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=hare@suse.de \
--cc=hch@infradead.org \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ronniesahlberg@gmail.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.