xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@novell.com>
To: Samuel Kvasnica <bugreports@list.ims.co.at>
Cc: xen-devel@lists.xensource.com
Subject: Re: vscsi 2TB patches
Date: Tue, 04 Jan 2011 09:47:46 +0000	[thread overview]
Message-ID: <4D22FAD2020000780002A28C@vpn.id2.novell.com> (raw)
In-Reply-To: <4D222D71.9020508@list.ims.co.at>

>>> On 03.01.11 at 21:11, Samuel Kvasnica <bugreports@list.ims.co.at> wrote:
> Hello xen developers,
> 
> the current xen vscsi driver implementation has a nasty >2TB limitation.
> Both the
> backend and frontend driver need a patch - included in the attachments.
> 
> Basically, for the frontend, just the max_cmd_len needs to be set correctly.
> For for the backend, at least the READ_16 and WRITE_16 scsi commands
> vere missing.
> I also enabled/added some more scsi commands to allow tape drives and
> autoloader
> work properly.
> 
> Could please somebody here take care to add this to mainstream code ?
> SuSE people were not interested really and the original author is not

Sort of interesting a statement - iirc we responded that we'd take
the changes once someone knowing the code reviewed them, and
suggested that you post them here (which now you did, but you'll
need to at least one more time to get thing into proper shape as
pointed out by Pasi).

> really known, i.e. "Copyright by Fujitsu Limited". I'm really sick of

The original scsiback and scsifront commits say

Signed-off-by: Tomonari Horikoshi <t.horikoshi@jp.fujitsu.com>
Signed-off-by: Jun Kamada <kama@jp.fujitsu.com>

Maybe you want to Cc them when you resubmit.

> patching every new kernel over and over...

Understandable.

Jan

  parent reply	other threads:[~2011-01-04  9:47 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-03 20:11 vscsi 2TB patches Samuel Kvasnica
2011-01-03 23:06 ` Pasi Kärkkäinen
2011-01-04 11:24   ` Samuel Kvasnica
2011-01-04 11:44     ` Jan Beulich
     [not found]       ` <4D231A46.2000209@list.ims.co.at>
     [not found]         ` <4D232ADB020000780002A33B@vpn.id2.novell.com>
     [not found]           ` <4D2321DE.9030706@list.ims.co.at>
     [not found]             ` <4D233968020000780002A36E@vpn.id2.novell.com>
2011-01-04 14:46               ` Samuel Kvasnica
2011-01-04 14:55                 ` Jan Beulich
2011-01-04 11:47     ` Jan Beulich
2011-01-04 13:03       ` Samuel Kvasnica
2011-01-04 13:07         ` Jan Beulich
2011-01-04 13:23           ` Samuel Kvasnica
2011-01-04 14:06             ` Jan Beulich
2011-01-11 16:26             ` Jan Beulich
2011-01-18 11:45             ` Jan Beulich
2011-01-24 12:24               ` Samuel Kvasnica
2011-01-04  9:47 ` Jan Beulich [this message]
2011-01-04 12:57   ` Samuel Kvasnica
2011-01-04 13:01     ` Jan Beulich

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=4D22FAD2020000780002A28C@vpn.id2.novell.com \
    --to=jbeulich@novell.com \
    --cc=bugreports@list.ims.co.at \
    --cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).