[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY2PR0301MB1654E0BA47F3D2CC6D83BD64A0D90@BY2PR0301MB1654.namprd03.prod.outlook.com>
Date: Wed, 27 Jan 2016 23:09:29 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Olaf Hering <olaf@...fle.de>,
James Bottomley <James.Bottomley@...senPartnership.com>
CC: Haiyang Zhang <haiyangz@...rosoft.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>
Subject: RE: [PATCH] storvsc: use small sg_tablesize on x86
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@...fle.de]
> Sent: Monday, January 25, 2016 12:35 AM
> To: James Bottomley <James.Bottomley@...senPartnership.com>
> Cc: KY Srinivasan <kys@...rosoft.com>; Haiyang Zhang
> <haiyangz@...rosoft.com>; linux-kernel@...r.kernel.org; linux-
> scsi@...r.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.
Regards,
K. Y
>
> Olaf
Powered by blists - more mailing lists