All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Tucker <tom@opengridcomputing.com>
To: Wolfgang Walter <wolfgang.walter@studentenwerk.mhn.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: Question about svc_age_temp_sockets
Date: Mon, 10 Sep 2007 09:04:37 -0500	[thread overview]
Message-ID: <1189433077.12145.8.camel@trinity.ogc.int> (raw)
In-Reply-To: <200709101033.13929.wolfgang.walter@studentenwerk.mhn.de>

On Mon, 2007-09-10 at 10:33 +0200, Wolfgang Walter wrote:
> > I'm confused about how svc_age_temp_sockets is supposed to work. From my
> > reading, the timer fires every 6 minutes and calls the svc_age_temp_sockets
> > function. This function sweeps the tempsocks list and unconditionally
> > test_and_sets every transport SK_OLD. If it was the first to set it, it
> > will test if the transport's not busy and then shut it down. So here's what
> > I don't get:
> >
> > - A transport that was added 5 minutes into the timer period, could get
> > shut down after only a minute of idleness
> >
> > - A transport that was busy may _never_ get shutdown because it will
> > already have it's SK_OLD bit set when it comes back through 6 minutes
> > later. If no more requests ever arrive from the client, the SK_OLD bit will
> > never get reset and the test_and_set check skips the transport if the bit's
> > already set.
> 
> Hmm, I think it works like that:
> 
> 		if (!test_and_set_bit(SK_OLD, &svsk->sk_flags))
>                         continue;
> 
> So: if SK_OLD is NOT already set then
> 		
> 		  !test_and_set_bit(SK_OLD, &svsk->sk_flags)
> 
> is true and therefor continue is executed (so the transport is not closed,
> only SK_OLD is set).
> 
> If SK_OLD is already set then this evaluates to false and the transport is 
> removed. This means that SK_OLD was set when the timer run the last time and 
> there was no request has arrived since then.

You're right, I misread the !. Duh. So the observation is that it takes
between 6 and 12 minutes to shut down the transport. What does
Connectathon consider reasonable variability?

> 
> >
> > - There's a check for a zero sk_inuse count. I don't see a legitimate way
> > for a socket to be on the tempsocks list with a zero refcount.
> >
> 
> This is something I don't understand, too. See my posting:
> 
> http://marc.info/?l=linux-nfs&m=118927571630268&w=4
> 
> As far as I see it does not work.
> 
> Regards,


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2007-09-10 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-10  8:33 Question about svc_age_temp_sockets Wolfgang Walter
2007-09-10 14:04 ` Tom Tucker [this message]
2007-09-14  9:19 ` Greg Banks
  -- strict thread matches above, loose matches on Subject: below --
2007-09-09 17:33 Tom Tucker
2007-09-14  9:16 ` Greg Banks

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=1189433077.12145.8.camel@trinity.ogc.int \
    --to=tom@opengridcomputing.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=wolfgang.walter@studentenwerk.mhn.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.