From: Alan Stern <stern@rowland.harvard.edu>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: Jan Engelhardt <jengelh@medozas.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
<linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
<linux-rt-users@vger.kernel.org>
Subject: Re: Large amount of scsi-sgpool objects
Date: Tue, 3 Mar 2009 12:59:37 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44L0.0903031256300.3274-100000@iolanthe.rowland.org> (raw)
In-Reply-To: <49AD59B4.1060304@panasas.com>
On Tue, 3 Mar 2009, Boaz Harrosh wrote:
> Jan Engelhardt wrote:
> > On Tuesday 2009-03-03 16:21, James Bottomley wrote:
> >>>> $ slabtop
> >>>> OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
> >>>> 818616 818616 100% 0.16K 34109 24 136436K sgpool-8
> >>>> 253692 253692 100% 0.62K 42282 6 169128K sgpool-32
> >>>> 52017 52016 99% 2.50K 17339 3 138712K sgpool-128
> >>>> 26220 26219 99% 0.31K 2185 12 8740K sgpool-16
> >>>> 8927 8574 96% 0.03K 79 113 316K size-32
> >>> Looks like a leak, by failing to call scsi_release_buffers()
> >>> somehow. (Which was changed recently)
> >> Firstly, I have to say I don't see this in the mainline tree, so could
> >> you try that with your setup just to verify (git head at 2.6.29-rc6).
> >
> > Yes, looking at the rt patch (in broken-out it's in origin.diff),
> > it seems a bit obvious - the scsi_release_buffers is not called anymore:
> >
> >
> > diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
> > index 940dc32..d4c6ac3 100644
> > --- a/drivers/scsi/scsi_lib.c
> > +++ b/drivers/scsi/scsi_lib.c
> > @@ -703,71 +703,6 @@ void scsi_run_host_queues(struct Scsi_Host *shost)
> >
> > static void __scsi_release_buffers(struct scsi_cmnd *, int);
> >
> > -/*
> > - * Function: scsi_end_request()
> > - *
> > - * Purpose: Post-processing of completed commands (usually invoked at end
> > - * of upper level post-processing and scsi_io_completion).
> > - *
> > - * Arguments: cmd - command that is complete.
> > - * error - 0 if I/O indicates success, < 0 for I/O error.
> > - * bytes - number of bytes of completed I/O
> > - * requeue - indicates whether we should requeue leftovers.
> > - *
> > - * Lock status: Assumed that lock is not held upon entry.
> > - *
> > - * Returns: cmd if requeue required, NULL otherwise.
> > - *
> > - * Notes: This is called for block device requests in order to
> > - * mark some number of sectors as complete.
> > - *
> > - * We are guaranteeing that the request queue will be goosed
> > - * at some point during this call.
> > - * Notes: If cmd was requeued, upon return it will be a stale pointer.
> > - */
> > -static struct scsi_cmnd *scsi_end_request(struct scsi_cmnd *cmd, int error,
> > - int bytes, int requeue)
> > -{
> > - struct request_queue *q = cmd->device->request_queue;
> > - struct request *req = cmd->request;
> > -
> > - /*
> > - * If there are blocks left over at the end, set up the command
> > - * to queue the remainder of them.
> > - */
> > - if (blk_end_request(req, error, bytes)) {
> > - int leftover = (req->hard_nr_sectors << 9);
> > -
> > - if (blk_pc_request(req))
> > - leftover = req->data_len;
> > -
> > - /* kill remainder if no retrys */
> > - if (error && scsi_noretry_cmd(cmd))
> > - blk_end_request(req, error, leftover);
> > - else {
> > - if (requeue) {
> > - /*
> > - * Bleah. Leftovers again. Stick the
> > - * leftovers in the front of the
> > - * queue, and goose the queue again.
> > - */
> > - scsi_release_buffers(cmd);
> > - scsi_requeue_command(q, cmd);
> > - cmd = NULL;
> > - }
> > - return cmd;
> > - }
> > - }
> > -
> > - /*
> > - * This will goose the queue request function at the end, so we don't
> > - * need to worry about launching another command.
> > - */
> > - __scsi_release_buffers(cmd, 0);
> > - scsi_next_command(cmd);
> > - return NULL;
> > -}
> > -
> > static inline unsigned int scsi_sgtable_index(unsigned short nents)
> > {
> > unsigned int index;
> > @@ -929,7 +864,6 @@ static void scsi_end_bidi_request(struct scsi_cmnd *cmd)
> > void scsi_io_completion(struct scsi_cmnd *cmd, unsigned int good_bytes)
> > {
> > int result = cmd->result;
> > - int this_count;
> > struct request_queue *q = cmd->device->request_queue;
> > struct request *req = cmd->request;
> > int error = 0;
> > @@ -980,18 +914,30 @@ void scsi_io_completion(struct scsi_cmnd *cmd, unsigned int good_bytes)
> > SCSI_LOG_HLCOMPLETE(1, printk("%ld sectors total, "
> > "%d bytes done.\n",
> > req->nr_sectors, good_bytes));
> > -
> > - /* A number of bytes were successfully read. If there
> > - * are leftovers and there is some kind of error
> > - * (result != 0), retry the rest.
> > - */
> > - if (scsi_end_request(cmd, error, good_bytes, result == 0) == NULL)
> > + if (blk_end_request(req, error, good_bytes) == 0) {
> > + /* This request is completely finished; start the next one */
> > + scsi_next_command(cmd);
> > return;
> > - this_count = blk_rq_bytes(req);
> > + }
> You lost me. Why does rt needs to patch scsi_io_completion at all?
> You should remove any rt patches that modify scsi_lib.c and revert to
> vanilla 2.6.29-rc6 (scsi wise that is).
>
> The above diff looks like something that was sent in the past to the mailing
> list, but only half of it. It was sent by Alan Stern. It might patch but
> it is not applicable any more because of changes made since.
That's right; it is an old version of a patch which no longer applies
to the current kernel (the __scsi_release_buffers() call was added
after that patch was written). An updated version of the patch has
been submitted here:
http://marc.info/?l=linux-scsi&m=123507641620649&w=2
Alan Stern
next prev parent reply other threads:[~2009-03-03 17:59 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-03 1:28 Large amount of scsi-sgpool objects Jan Engelhardt
2009-03-03 9:31 ` Boaz Harrosh
2009-03-03 15:21 ` James Bottomley
2009-03-03 16:08 ` Jan Engelhardt
2009-03-03 16:24 ` Boaz Harrosh
2009-03-03 17:59 ` Alan Stern [this message]
2009-03-03 20:56 ` Ingo Molnar
2009-03-03 21:06 ` Alan Stern
2009-03-03 16:25 ` James Bottomley
2009-03-03 17:19 ` Thomas Gleixner
2009-03-03 22:07 ` [BUG] 2.6.29-rc6-2450cf in scsi_lib.c (was: Large amount of scsi-sgpool)objects Thomas Gleixner
2009-03-03 22:22 ` Jan Engelhardt
2009-03-03 23:07 ` Thomas Gleixner
2009-03-03 22:26 ` James Bottomley
2009-03-04 2:01 ` Thomas Gleixner
2009-03-04 18:55 ` James Bottomley
2009-03-04 21:45 ` Thomas Gleixner
2009-03-04 22:56 ` James Bottomley
2009-03-05 0:13 ` James Bottomley
2009-03-05 8:36 ` FUJITA Tomonori
2009-03-05 8:39 ` FUJITA Tomonori
2009-03-05 9:29 ` FUJITA Tomonori
2009-03-05 10:09 ` Jens Axboe
2009-03-05 10:14 ` Jens Axboe
2009-03-05 10:27 ` FUJITA Tomonori
2009-03-05 10:30 ` Jens Axboe
2009-03-05 10:41 ` FUJITA Tomonori
2009-03-05 11:10 ` Jens Axboe
2009-03-05 11:40 ` FUJITA Tomonori
2009-03-05 10:41 ` Ingo Molnar
2009-03-05 11:05 ` Jens Axboe
2009-03-05 11:07 ` Ingo Molnar
2009-03-05 12:09 ` Thomas Gleixner
2009-03-05 23:16 ` Thomas Gleixner
2009-03-05 19:32 ` Ingo Molnar
2009-03-05 10:15 ` Ingo Molnar
2009-03-03 19:22 ` Large amount of scsi-sgpool objects Ingo Molnar
2009-03-03 21:25 ` James Bottomley
2009-03-03 21:44 ` Ingo Molnar
2009-03-03 22:39 ` James Bottomley
2009-03-03 23:03 ` Ingo Molnar
2009-03-03 23:32 ` Stefan Richter
2009-03-03 23:48 ` Ingo Molnar
2009-03-04 6:39 ` Stefan Richter
2009-03-04 7:12 ` Mike Galbraith
2009-03-04 7:50 ` Stefan Richter
2009-03-04 8:00 ` Mike Galbraith
2009-03-04 9:06 ` Thomas Gleixner
2009-03-04 11:12 ` Ingo Molnar
2009-03-04 11:28 ` Stefan Richter
2009-03-04 11:47 ` Ingo Molnar
2009-03-04 12:02 ` Stefan Richter
2009-03-04 11:24 ` Ingo Molnar
2009-03-04 19:11 ` Andrew Morton
2009-03-04 20:09 ` Thomas Gleixner
2009-03-04 0:01 ` James Bottomley
2009-03-04 0:39 ` Ingo Molnar
2009-03-04 0:30 ` Thomas Gleixner
2009-03-04 0:47 ` Ingo Molnar
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=Pine.LNX.4.44L0.0903031256300.3274-100000@iolanthe.rowland.org \
--to=stern@rowland.harvard.edu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bharrosh@panasas.com \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-scsi@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;
as well as URLs for NNTP newsgroup(s).