linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'James Bottomley' <jejb@linux.vnet.ibm.com>,
	Johannes Thumshirn <jthumshirn@suse.de>,
	John Garry <john.garry@huawei.com>,
	Sabyasachi Gupta <sabyasachi.linux@gmail.com>,
	"satishkh@cisco.com" <satishkh@cisco.com>,
	"sebaddel@cisco.com" <sebaddel@cisco.com>,
	"kartilak@cisco.com" <kartilak@cisco.com>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Cc: "jrdr.linux@gmail.com" <jrdr.linux@gmail.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"brajeswar.linux@gmail.com" <brajeswar.linux@gmail.com>
Subject: RE: [PATCH] drivers/scsi/fnic/fnic_trace.c: Use vzalloc
Date: Wed, 14 Nov 2018 10:44:12 +0000	[thread overview]
Message-ID: <d5ff3e3cb7cb435a9eff8d159e85f704@AcuMS.aculab.com> (raw)
In-Reply-To: <1542125473.3042.6.camel@linux.vnet.ibm.com>

From: James Bottomley
> Sent: 13 November 2018 16:11
> 
> On Tue, 2018-11-13 at 16:53 +0100, Johannes Thumshirn wrote:
> > On 13/11/2018 16:44, John Garry wrote:
> > > On 13/11/2018 15:08, Sabyasachi Gupta wrote:
> [...]
> > > > -    fnic_trace_buf_p = (unsigned long)vmalloc((trace_max_pages *
> > > > PAGE_SIZE));
> > > > +    fnic_trace_buf_p = (unsigned long)vzalloc((trace_max_pages *
> > > > +                                PAGE_SIZE));
> > >
> > > If you remove the extra brackets in vzalloc() argument then you may
> > > not spill onto the next line.
> >
> > And remove the unnecessary cast. vzalloc() (just like vmalloc())
> > returns a void*, so no reason to cast it.
> 
> This is incorrect advice: there's no need to cast it to other *pointer*
> types, but if you cast it to a non-pointer type (which this is doing)
> the compiler will complain if there is no explicit cast.

The real question is why is this code using 'unsigned long'
to hold pointers?

Never mind why it is allocating a large memory block then setting
up another array with pointers to every 64 bytes down it.

Also why default to 16 * PAGE_SIZE - that is silly if pages are big.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

      parent reply	other threads:[~2018-11-14 10:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 15:08 [PATCH] drivers/scsi/fnic/fnic_trace.c: Use vzalloc Sabyasachi Gupta
2018-11-13 15:44 ` John Garry
2018-11-13 15:53   ` Johannes Thumshirn
2018-11-13 16:04     ` Sabyasachi Gupta
2018-11-13 16:11     ` James Bottomley
2018-11-13 16:16       ` Johannes Thumshirn
2018-11-13 16:22         ` Sabyasachi Gupta
2018-11-13 16:25           ` Johannes Thumshirn
2018-11-14 10:44       ` David Laight [this message]

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=d5ff3e3cb7cb435a9eff8d159e85f704@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=brajeswar.linux@gmail.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=john.garry@huawei.com \
    --cc=jrdr.linux@gmail.com \
    --cc=jthumshirn@suse.de \
    --cc=kartilak@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sabyasachi.linux@gmail.com \
    --cc=satishkh@cisco.com \
    --cc=sebaddel@cisco.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).