From: Arjan van de Ven <arjan@infradead.org>
To: bhuvan.kumarmital@wipro.com
Cc: kernelnewbies@nl.linux.org, kernel-mentors@selenic.com,
linux-kernel@vger.kernel.org
Subject: Re: Expertise required:USB bulk-throughput and memory leak detection
Date: Mon, 26 Jun 2006 13:29:37 +0200 [thread overview]
Message-ID: <1151321378.3185.25.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <24ED22E506B5A042BF5B05B6B017D86C0A9016@PNE-HJN-MBX01.wipro.com>
On Mon, 2006-06-26 at 15:50 +0530, bhuvan.kumarmital@wipro.com wrote:
>
>
you made the same mistake here as on kernelnewbies.. you didn't post a
pointer to the source code ;)
> > -----Original Message-----
> > From: Bhuvan Kumarmital (WT01 - Semiconductors & Consumer
> > Electronics)
> > To: 'kernelnewbies@nl.linux.org'
> > Subject: Expertise required:USB bulk-throughput and memory
> > leak detection
> >
> >
> > My team is developing a device driver for a PCMCIA based
> > USB device. We're currently trying to test the performance of
> > our driver. However we're unable to figure out a reliable methods of:
> > 1.) detecting memory leaks caused by our driver code.
> > 2.) Neither have we been able to find a tool which shows %
> > utilisation of kernel memory used by our driver.(kernel
> > memory monitoring)
> > 3.) Throughput calculation of bulk data transfer is also not
> > precise. We still rely on measuring time on stop watch, while
> > Transferring data.
> >
> > About the memory monitoring, there are quite a few tools
> > available at the application level (like free and top which
> > are available with the operating system itself). But none for
> > the kernel level.
> >
> > Please suggest other feasible ways of detecting leaks and
> > monitoring kernel memory utilisation for kernel 2.6.15.4 on
> > fedora core 4.
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2006-06-26 11:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-26 10:20 bhuvan.kumarmital
2006-06-26 11:29 ` Arjan van de Ven [this message]
2007-02-21 17:21 ` Michael Richardson
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=1151321378.3185.25.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=bhuvan.kumarmital@wipro.com \
--cc=kernel-mentors@selenic.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.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®