From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: "gregkh@suse.de" <gregkh@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"virtualization@lists.osdl.org" <virtualization@lists.osdl.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"ohering@suse.com" <ohering@suse.com>,
"hch@infradead.org" <hch@infradead.org>
Subject: RE: [PATCH 1/1] Staging: hv: storvsc: Move the storage driver out of the staging area
Date: Fri, 18 Nov 2011 11:00:31 -0600 [thread overview]
Message-ID: <1321635631.3022.44.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <6E21E5352C11B742B20C142EB499E0481AA6D232@TK5EX14MBXC128.redmond.corp.microsoft.com>
On Fri, 2011-11-18 at 04:53 +0000, KY Srinivasan wrote:
> > I still think you need to disable clustering and junk the bvec merge
> > function. Your object seems to be to accumulate in page size multiples
> > (and not aggregate over this) ... that's what clustering is designed to
> > do.
>
> As part of addressing your first round of comments, I experimented with your
> suggestions and I could not get rid of the code that does the bounce buffer handling.
> I could generate I/O patterns that would require bounce buffer handling with your
> suggestions in place.
There are two separate things here. One is the scatter gather list
bounce buffer processing, which is a bit nasty, but if you want to use <
4kb block size filesystems, I suppose I have to accept that you need it
(although since it's a global fault of the hypervisor, perhaps it should
sit in the hypervisor interface layer, so that every SG based transport
can use it). The other is the biovec merge function addition. The
purpose of this function seems to be to ensure you get one SG entry for
every page (if I read it right)? In that case, you don't need any of
this special casing. The flag DISABLE_CLUSTERING achieves the same
thing.
James
next prev parent reply other threads:[~2011-11-18 17:00 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-08 18:13 K. Y. Srinivasan
2011-11-17 18:26 ` James Bottomley
2011-11-18 4:53 ` KY Srinivasan
2011-11-18 17:00 ` James Bottomley [this message]
2011-11-18 23:28 ` KY Srinivasan
2011-11-30 13:46 ` KY Srinivasan
2011-12-01 13:43 K. Y. Srinivasan
2011-12-07 16:16 K. Y. Srinivasan
2011-12-08 10:37 ` Rolf Eike Beer
2012-01-12 21:15 K. Y. Srinivasan
2012-01-14 16:42 ` Christoph Hellwig
2012-01-14 20:31 ` KY Srinivasan
2012-01-16 15:29 ` Christoph Hellwig
2012-01-16 22:47 ` KY Srinivasan
2012-01-16 22:55 ` KY Srinivasan
2012-01-25 15:29 ` KY Srinivasan
2012-01-25 15:43 ` Christoph Hellwig
2012-01-25 15:51 ` Greg KH
2012-01-25 15:59 ` James Bottomley
2012-01-25 17:03 ` Greg KH
2012-01-25 17:12 ` James Bottomley
2012-01-25 17:13 ` KY Srinivasan
2012-01-25 19:22 ` KY Srinivasan
2012-01-25 21:13 ` KY Srinivasan
2012-01-26 14:11 ` KY Srinivasan
2012-01-25 18:29 K. Y. Srinivasan
2012-01-26 16:07 ` James Bottomley
2012-01-26 17:17 ` Rolf Eike Beer
2012-01-26 17:24 ` KY Srinivasan
2012-02-09 20:04 K. Y. Srinivasan
2012-02-09 20:04 ` Greg KH
2012-02-09 20:18 ` James Bottomley
2012-02-09 20:21 ` KY Srinivasan
2012-02-09 20:40 ` James Bottomley
2012-02-09 20:24 ` Greg KH
2012-02-09 20:43 ` KY Srinivasan
2012-02-09 20:45 ` James Bottomley
2012-02-09 20:51 ` KY Srinivasan
2012-02-09 22:13 ` KY Srinivasan
2012-02-10 11:12 ` KY Srinivasan
2012-02-09 22:14 K. Y. Srinivasan
2012-02-10 18:02 ` Greg KH
2012-02-13 18:59 ` KY Srinivasan
2012-02-13 19:28 ` James Bottomley
2012-02-13 19:31 ` KY Srinivasan
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=1321635631.3022.44.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@suse.de \
--cc=hch@infradead.org \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=ohering@suse.com \
--cc=virtualization@lists.osdl.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
all inboxes | Powered by JetHome®