All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Mark Gross <mgross@unix-os.sc.intel.com>
Cc: Pavel Machek <pavel@suse.cz>,
	"Vamsi Krishna S." <vamsi_krishna@in.ibm.com>,
	"Gross, Mark" <mark.gross@intel.com>,
	linux-kernel@vger.kernel.org, r1vamsi@in.ibm.com
Subject: Re: PATCH Multithreaded core dumps for the 2.5.17 kernel  was ....RE:    PATCH Multithreaded core dump support for the 2.5.14 (and 15) kernel.
Date: Wed, 22 May 2002 19:22:02 +0000	[thread overview]
Message-ID: <20020522192202.D229@toy.ucw.cz> (raw)
In-Reply-To: <59885C5E3098D511AD690002A5072D3C057B489B@orsmsx111.jf.intel.com> <200205220748.g4M7mc2157646@northrelay01.pok.ibm.com> <20020522141747.G37@toy.ucw.cz> <200205222043.g4MKhsw06808@unix-os.sc.intel.com>

Hi!

> > > Nice. This also closes another issue pointed out: freezing
> > > a process while it is holding the mmap_sem, which may be needed later
> > > while collecting thread registers on IA64.
> > >
> > > Now that Linus has accepted Pavel's swsusp, do you have any thoughts
> > > on using Pavel's scheme to freeze processes?
> >
> > I attempt half of signal delivery to the threads, but that should not be
> > a problem. Currently freezing stuff is there only for CONFIG_SWSUSP case,
> > but it is probably small enough to be there unconditionaly.
> > 								Pavel
> 
> I think that although my tcore_suspend_threads and Pavel's freeze_processes 
> have similar results, I don't think using Pavel's approach for the core dump 
> is a good idea.
> 
> 1) SMP is a stability problem.  I want TCore to work for 2.4x kernels  
> soon. 
> 2) To avoid the issues with I/O bound threads waking up, Pavel's design waits 
> for the signal to get them running and then drops them in the "refrigerator". 
>  
> My design is explicitly going for the most accurate core dump it can.  
> If I need to wait for processes to wake up and get frozen on a large SMB box 
> then we can loose a lot of accuracy.

Okay.

> I do however; think Pavels work could benefit from using some of my approach. 
>  It might simplify all those places where his patch tests p->state | 
> PK_FREEZE and then calls  refrigerator.   It perhaps make it work better for 
> SMP if software suspend is considered a usefull feature on a SMP systems.

swsusp definitely is usable on SMP system. Take server with not-hotpluggable
pci andpci card you want to add. How do you add it with minimum impact on
users?

suspend/add card/resume
									Pavel
PS: I did not yet test swsusp on SMP, through. But I'd like it to work.
-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  reply	other threads:[~2002-05-23 21:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 23:08 PATCH Multithreaded core dumps for the 2.5.17 kernel was ....RE: PATCH Multithreaded core dump support for the 2.5.14 (and 15) kernel Gross, Mark
2002-05-22  7:56 ` Vamsi Krishna S.
2002-05-22 14:11   ` Pavel Machek
2002-05-22 14:17   ` Pavel Machek
2002-05-22 17:43     ` Mark Gross
2002-05-22 19:22       ` Pavel Machek [this message]
2002-05-23 21:03         ` Martin Dalecki
2002-05-23 22:27           ` Pavel Machek
2002-05-22 22:07       ` PATCH Multithreaded core dumps for the 2.5.17 kernel was ....RE: PATCH Multithreaded core dump support for the 2.5.14 (aO Alan Cox
2002-05-22 23:29         ` Daniel Jacobowitz
2002-05-23 10:07         ` Pavel Machek
2002-05-22 23:32 ` PATCH Multithreaded core dumps for the 2.5.17 kernel was ....RE: PATCH Multithreaded core dump support for the 2.5.14 (and 15) kernel Daniel Jacobowitz
2002-05-22 21:09   ` Mark Gross
2002-05-23  1:12     ` Daniel Jacobowitz
2002-05-23 13:12       ` Mark Gross

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=20020522192202.D229@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.gross@intel.com \
    --cc=mgross@unix-os.sc.intel.com \
    --cc=r1vamsi@in.ibm.com \
    --cc=vamsi_krishna@in.ibm.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 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.