From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: mc@linux.vnet.ibm.com
Cc: stefanha@linux.vnet.ibm.com, linuxram@us.ibm.com,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
senwang@linux.vnet.ibm.com
Subject: Re: [PATCH] SCSI: Add SG_GET_SG_MAX_SEGMENT_SIZE ioctl to sg device
Date: Tue, 03 Jul 2012 12:01:12 +0400 [thread overview]
Message-ID: <1341302472.3319.26.camel@dabdike> (raw)
In-Reply-To: <1341302003.17396.20.camel@mengcong>
On Tue, 2012-07-03 at 15:53 +0800, Cong Meng wrote:
> On Mon, 2012-07-02 at 12:18 +0100, James Bottomley wrote:
> > On Mon, 2012-07-02 at 17:20 +0800, Cong Meng wrote:
> > > Add a new ioctl cmd to get the max segment size. It's useful in
> > > virtualization environment for guest to know the queue limits, so
> > > that the guest kicks off legal scsi command to a sg device.
> >
> > What's wrong with simply looking in the /sys for this? Plus, if you can
>
> Adding this ioctl is a big convenience for the programs, qemu
> in my case, to which parameter that likes '/dev/sgX' is given.
> With this ioctl, those programs only need to issue an ioctl to
> get the queue limit.
I don't need to know why you need the information, I accept that it's
useful
> Otherwise, 'dev/sgX' is needed to convert
> to /sys path, then open and read it.
Well, yes, what's the problem?
> In addition, the potential variation and exceptional situation
> of sys FS, EX mount path, are needed to consider as well.
> Is my justification acceptable?
No. I need to know why you can't get it out of sysfs. We put a whole
lot of stuff into sysfs to avoid the need to add extra ioctls. There
need to be a really good reason why /sys doesn't work.
James
> > come up with a justifiable reason, this needs to be in block as well so
> > we can send it to all SCSI devices regardless of what ULD people use.
> I can do it.
>
> Thanks.
> Cong.
> >
> > James
> >
> >
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-07-03 8:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 9:20 [PATCH] SCSI: Add SG_GET_SG_MAX_SEGMENT_SIZE ioctl to sg device Cong Meng
2012-07-02 11:18 ` James Bottomley
2012-07-03 7:53 ` Cong Meng
2012-07-03 8:01 ` James Bottomley [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=1341302472.3319.26.camel@dabdike \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=mc@linux.vnet.ibm.com \
--cc=senwang@linux.vnet.ibm.com \
--cc=stefanha@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox