From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: KY Srinivasan <kys@microsoft.com>, Olaf Hering <olaf@aepfle.de>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] storvsc: use small sg_tablesize on x86
Date: Wed, 27 Jan 2016 22:00:59 -0800 [thread overview]
Message-ID: <1453960859.2322.58.camel@HansenPartnership.com> (raw)
In-Reply-To: <BY2PR0301MB1654E0BA47F3D2CC6D83BD64A0D90@BY2PR0301MB1654.namprd03.prod.outlook.com>
On Wed, 2016-01-27 at 23:09 +0000, KY Srinivasan wrote:
>
> > -----Original Message-----
> > From: Olaf Hering [mailto:olaf@aepfle.de]
> > Sent: Monday, January 25, 2016 12:35 AM
> > To: James Bottomley <James.Bottomley@HansenPartnership.com>
> > Cc: KY Srinivasan <kys@microsoft.com>; Haiyang Zhang
> > <haiyangz@microsoft.com>; linux-kernel@vger.kernel.org; linux-
> > scsi@vger.kernel.org
> > Subject: Re: [PATCH] storvsc: use small sg_tablesize on x86
> >
> > On Fri, Oct 02, Olaf Hering wrote:
> >
> > > On Thu, Oct 01, James Bottomley wrote:
> > >
> > > > On Thu, 2015-10-01 at 20:30 +0000, KY Srinivasan wrote:
> > >
> > > > > > +#if defined(CONFIG_X86_32)
> > >
> > > > Um, this is a bit architecture specific (I know Azure is x86,
> > > > but
> > > > still). Can you make the define check CONFIG_32BIT rather than
> > > > CONFIG_X86_32?
> > >
> > > According to arch/x86/Kconfig there is no such thing.
> >
> > What is the status of this change? Looks like there is nothing more
> > to do on my side.
>
> Olaf,
>
> We do have the config option: CONFIG_X86_64. Perhaps we could use
> this. Could you resubmit the patch with this change.
It's not really architecture independent, is it? Just use the bit
width config.
James
next prev parent reply other threads:[~2016-01-28 6:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 10:06 Olaf Hering
2015-10-01 20:30 ` KY Srinivasan
2015-10-01 20:51 ` James Bottomley
2015-10-01 21:27 ` KY Srinivasan
2015-10-02 17:14 ` Olaf Hering
2016-01-25 8:35 ` Olaf Hering
2016-01-27 23:09 ` KY Srinivasan
2016-01-28 6:00 ` James Bottomley [this message]
2016-01-28 6:48 ` Olaf Hering
2016-01-28 15:37 ` James Bottomley
2016-02-26 22:11 ` KY Srinivasan
2016-05-16 20:26 Joseph Salisbury
2016-05-17 13:07 ` Olaf Hering
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=1453960859.2322.58.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=olaf@aepfle.de \
/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
Powered by JetHome