From: Julia Lawall <julia.lawall@lip6.fr>
To: "Drokin, Oleg" <oleg.drokin@intel.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>,
"Dilger, Andreas" <andreas.dilger@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"<HPDD-discuss@lists.01.org>" <HPDD-discuss@ml01.01.org>,
"<devel@driverdev.osuosl.org>" <devel@driverdev.osuosl.org>,
"<linux-kernel@vger.kernel.org>" <linux-kernel@vger.kernel.org>
Subject: Re: lustre: question about lov_request.c
Date: Sun, 7 Jun 2015 23:06:32 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1506072306190.2081@localhost6.localdomain6> (raw)
In-Reply-To: <4ED30946-5333-4684-9498-B734D991847A@intel.com>
On Sun, 7 Jun 2015, Drokin, Oleg wrote:
> Hello!
>
> You are right, set_pga seems to be a dead member. It was alive a once, but somehow not fully removed now,
> so it's safe to drop the whole if and also the struct member itself.
> set_oabufs could be dropped as well.
Thanks. I will do that.
julia
>
> Thanks.
>
> Bye,
> Oleg
> On Jun 7, 2015, at 4:11 PM, Julia Lawall wrote:
>
> > Hello,
> >
> > The function lov_finish_set in
> > drivers/staging/lustre/lustre/lov/lov_request.c contains the code:
> >
> > if (set->set_pga) {
> > int len = set->set_oabufs * sizeof(*set->set_pga);
> > OBD_FREE_LARGE(set->set_pga, len);
> > }
> >
> > If I change the call to OBD_FREE_LARGE to kvfree, then len is not useful
> > any more. But actually, at least with grep, I can't find anywhere that
> > either the set_pga field or the set_oabufs field is set. Am I missing
> > something, or can the whole if be removed? Can these two fields go too?
> >
> > thanks,
> > julia
>
>
next prev parent reply other threads:[~2015-06-07 21:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-07 20:11 Julia Lawall
2015-06-07 20:58 ` Drokin, Oleg
2015-06-07 21:06 ` Julia Lawall [this message]
2015-06-08 7:24 ` Julia Lawall
2015-06-08 7:58 ` Drokin, Oleg
2015-06-23 6:23 ` lustre: LIBCFS_ALLOC Julia Lawall
2015-06-23 8:30 ` Drokin, Oleg
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=alpine.DEB.2.02.1506072306190.2081@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=HPDD-discuss@ml01.01.org \
--cc=andreas.dilger@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg.drokin@intel.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
all inboxes | Powered by JetHome®