Re: How do I find out who uses swap?
On Wed, Jan 26, 2005 at 02:11:56PM +0100, Maciej Soltysiak wrote: > Hi, > > I have a problem for some time with that the amount of swap > being used constantly increases up to the moment where > the swap is used in 100% and the machine deadlocks. > > How do I find out which proceses use swap and in what amount? > > I tried using top and sorting by SWAP, it shows this: > PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ SWAP COMMAND > 3390 ncg 15 0 72504 3380 1720 S 0.0 0.7 0:00.76 67m ncgserver > 24718 mysql 15 0 68056 7364 2232 S 0.0 1.4 2:30.70 59m mysqld > 582 fallen16 0 30396 568 480 S 0.0 0.1 0:02.40 29m sc_serv > 624 vpopmail 16 0 31124 1736 1436 S 0.0 0.3 0:01.99 28m spamd > 31765 solt 16 0 29916 1020 616 S 0.0 0.2 0:02.25 28m sc_serv > 3348 bind 22 0 31604 3872 1472 S 0.0 0.8 0:48.84 27m named > 24021 root 16 0 32976 10m 7228 S 0.0 2.1 0:01.99 21m apache > 13066 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.62 21m apache > 13103 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.61 21m apache > 13104 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.60 21m apache > 13099 www-data 16 0 33104 10m 7276 S 0.3 2.2 0:00.63 21m apache > 13142 www-data 16 0 33104 10m 7276 S 0.0 2.2 0:00.61 21m apache > 29898 www-data 16 0 33108 11m 7580 S 0.0 2.2 0:00.01 21m apache > 13061 www-data 16 0 34492 12m 7700 S 0.0 2.5 0:00.56 21m apache > 13057 www-data 15 0 35076 13m 7696 S 0.0 2.6 0:00.78 21m apache > 23259 www-data 16 0 36344 14m 7784 S 0.0 2.9 0:01.15 21m apache > 13062 www-data 15 0 37812 15m 7868 S 0.0 3.2 0:01.03 20m apache ^^^ look here > > Or should I look at VIRT or MEM ? > I am confused. man 1 top -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: List of things requested by lkml for reiser4 inclusion (to review)
On Fri, Sep 09, 2005 at 10:36:06AM -0700, Hans Reiser wrote: > If we lose every remaining point of this list, we can generate a patch > in a few days, because the VFS work was the only substantive (in coding > hours) task, and it is done. Do I remember right that the submission > deadline is a week from Monday for 2.6.14 inclusion? No. 14 days from release date of 2.6.13, which was 8/29, so deadline is 9/12, this coming Monday. -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: List of things requested by lkml for reiser4 inclusion (to review)
On Fri, Sep 09, 2005 at 01:42:19PM -0700, Hans Reiser wrote: > Chris Shoemaker wrote: > > >On Fri, Sep 09, 2005 at 10:36:06AM -0700, Hans Reiser wrote: > > > > > >>If we lose every remaining point of this list, we can generate a patch > >>in a few days, because the VFS work was the only substantive (in coding > >>hours) task, and it is done. Do I remember right that the submission > >>deadline is a week from Monday for 2.6.14 inclusion? > >> > >> > > > >No. 14 days from release date of 2.6.13, which was 8/29, so deadline > >is 9/12, this coming Monday. > > > >-chris > > > > > > > > > IIRC, Linus announced that since he was going on vacation for 7 days, > this release only it would be 3 weeks, so it is a week from Monday that > we must submit by, yes? > > Hans On Thu Sep 08 2005 - 12:26:28 EST, Linus warned: > That release was ten days ago, so you've got four more days before I > don't want any big merges. Surely you know how to search LKML archives for any mail from Linus since the release of 2.6.13. It's only 2 mouse clicks if you know where to find the archives. (3 if you start from kernel.org) Getting lazy? -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] CodingStyle: Add information about trailing whitespace.
On Wed, Jun 27, 2007 at 10:59:20AM -0700, Josh Triplett wrote: > +Do not leave trailing whitespace at the ends of lines. Some editors with > +"smart" indentation will insert whitespace at the beginning of new lines as > +appropriate, so you can start typing the next line of code right away. > +However, some such editors do not remove the whitespace if you end up not > +putting a line of code there, such as if you leave a blank line. As a > result, > +you end up with lines containing trailing whitespace. > + > +Git will warn you about patches that introduce trailing whitespace, and can > +optionally strip the trailing whitespace for you; however, if applying a > series > +of patches, this may make later patches in the series fail by changing their > +context lines. What I'd really like to see is, _why_ is trailing whitespace considered harmful? Something about MUAs not preserving it or something? -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] CodingStyle: Add information about trailing whitespace.
On Wed, Jun 27, 2007 at 11:17:09AM -0700, Josh Triplett wrote: > On Wed, 2007-06-27 at 14:05 -0400, Chris Shoemaker wrote: > > On Wed, Jun 27, 2007 at 10:59:20AM -0700, Josh Triplett wrote: > > > +Do not leave trailing whitespace at the ends of lines. Some editors with > > > +"smart" indentation will insert whitespace at the beginning of new lines > > > as > > > +appropriate, so you can start typing the next line of code right away. > > > +However, some such editors do not remove the whitespace if you end up not > > > +putting a line of code there, such as if you leave a blank line. As a > > > result, > > > +you end up with lines containing trailing whitespace. > > > + > > > +Git will warn you about patches that introduce trailing whitespace, and > > > can > > > +optionally strip the trailing whitespace for you; however, if applying a > > > series > > > +of patches, this may make later patches in the series fail by changing > > > their > > > +context lines. > > > > What I'd really like to see is, _why_ is trailing whitespace > > considered harmful? Something about MUAs not preserving it or > > something? > > When the trailing whitespace later disappears, that change shows up in > diffs, and since you can't see the whitespace difference, it just looks > like a mysterious change until you check it more closely. Okay, but it seems like this is more of an argument that diffs containing lines that change only the trailing whitespace are considered harmful. I buy that, but I don't see why it follows that new code shouldn't have any trailing whitespace at all. > It also introduces gratuitous conflicts and other such annoyances. I don't get this part. Only changes can create conflicts. Are there some editors (or MUAs) that change trailing whitespace without being told to? (And I'm not even talking about your warning about conflicts created by applying stripped versions of early patches in a series - that's just self-inflicted pain.) -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
