public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Juergen Gross <JGross@suse.com>
Cc: xen-devel@lists.xen.org, JBottomley@parallels.com,
	linux-scsi@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH 1/4] Add XEN pvSCSI protocol description
Date: Mon, 30 Jun 2014 12:29:20 +0100	[thread overview]
Message-ID: <53B16630020000780001E830@mail.emea.novell.com> (raw)
In-Reply-To: <53B14798.70303@suse.com>

>>> On 30.06.14 at 13:18, <JGross@suse.com> wrote:
> On 06/30/2014 01:02 PM, Jan Beulich wrote:
>>>>> On 27.06.14 at 19:11, <konrad.wilk@oracle.com> wrote:
>>> On Fri, Jun 27, 2014 at 04:34:33PM +0200, jgross@suse.com wrote:
>>>> +/*
>>>> + * Maximum scatter/gather segments per request.
>>>> + *
>>>> + * Considering balance between allocating at least 16 "vscsiif_request"
>>>> + * structures on one page (4096 bytes) and the number of scatter/gather
>>>> + * elements needed, we decided to use 26 as a magic number.
>>>> + */
>>>> +#define VSCSIIF_SG_TABLESIZE		26
>>>> +
>>>> +/*
>>>> + * based on Linux kernel 2.6.18
>>>
>>> This being a bit more .. new, - do these sizes make sense anymore?
>>> Should they be extended a bit? Or have support for using the
>>> old ones (as default) and then negotiate new sizes with the kernel?
>>> (If of course there is a difference?)
>>
>> As Jürgen already said (and as you should have noticed yourself) -
>> this is an interface definition that we can't just change. Negotiation
>> of larger counts is an option, which is what VSCSIIF_ACT_SCSI_SG_PRESET
>> is intended for (the implementation of which isn't part of this patchset
>> afaics, but could be made available on top of it).
> 
> I don't think this is the proper way to handle larger SG lists. The
> VSCSIIF_ACT_SCSI_SG_PRESET option would just bump the maximum length
> up to 31 (currently 26). Or was it thought to be incremental (multiple
> presets for one request)?

Yes, that's how it's to be used. See xen-vscsi-large-requests.patch
it the newer of our trees.

> I'd rather add a way to specify SG lists
> residing in an own (granted) page (or even multiple pages). This would
> allow 512*26 SG entries without having to change the request structure.
> The capability to handle this feature could be indicated via xenstore.

And yes, considering the similar changes in blkif I agree that this
would be the preferred method today. That patch, however,
predates those blkif enhancements.

Jan
--
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

  reply	other threads:[~2014-06-30 11:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-27 14:34 Add XEN pvSCSI support jgross
2014-06-27 14:34 ` [PATCH 1/4] Add XEN pvSCSI protocol description jgross
2014-06-27 17:11   ` [Xen-devel] " Konrad Rzeszutek Wilk
2014-06-30  8:26     ` Juergen Gross
2014-06-30 11:02     ` Jan Beulich
2014-06-30 11:18       ` Juergen Gross
2014-06-30 11:29         ` Jan Beulich [this message]
2014-06-27 14:34 ` [PATCH 2/4] Introduce xen-scsifront module jgross
2014-06-30 13:35   ` [Xen-devel] " David Vrabel
2014-06-30 13:51     ` Juergen Gross
2014-06-27 14:34 ` [PATCH 3/4] Introduce XEN scsiback module jgross
2014-06-28 18:09   ` Christoph Hellwig
2014-07-11  8:57     ` Juergen Gross
2014-07-11  9:04       ` Christoph Hellwig
2014-06-27 14:34 ` [PATCH 4/4] add xen pvscsi maintainer jgross
2014-06-27 17:13   ` Konrad Rzeszutek Wilk
2014-06-27 17:45 ` Add XEN pvSCSI support Pasi Kärkkäinen
2014-06-27 17:51   ` [Xen-devel] " Pasi Kärkkäinen

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=53B16630020000780001E830@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=JBottomley@parallels.com \
    --cc=JGross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=xen-devel@lists.xen.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