Re: hi

Re:⏰Hi

Grandios! http://knrsbwy.Merissa836.xyz/index ___ Bis bald nik_bin_nek_a...@yahoo.com

Re: Hi (Assigning NULL to variable after freeing it).

>> I have just started to contribute to linux kernel. I was thinking of >> giving a patch where a variable is made null after free if not already >> done. >> > General answer is no... unless that particular code expects a freed pointer > to be null. In many cases the code is written so that this

Re: Hi (Assigning NULL to variable after freeing it).

>> I have just started to contribute to linux kernel. I was thinking of >> giving a patch where a variable is made null after free if not already >> done. >> > General answer is no... unless that particular code expects a freed pointer > to be null. In many cases the code is written so that this

Re: Hi (Assigning NULL to variable after freeing it).

On 01/17/18 02:44, Jose Bale wrote: > Hi All, > > I have just started to contribute to linux kernel. I was thinking of > giving a patch where a variable is made null after free if not already > done. > > Some thing like this: > Original code: > kfree(x); > ...some other

Re: Hi (Assigning NULL to variable after freeing it).

On 01/17/18 02:44, Jose Bale wrote: > Hi All, > > I have just started to contribute to linux kernel. I was thinking of > giving a patch where a variable is made null after free if not already > done. > > Some thing like this: > Original code: > kfree(x); > ...some other

RE: Hi, Ingo, would you please help drop the TSC MSR calibration patch

Hi, > -Original Message- > From: Pan, Jacob jun > Sent: Tuesday, July 12, 2016 5:19 AM > To: Ingo Molnar > Cc: Chen, Yu C; 'Len Brown'; Jacob Pan; H. Peter Anvin; Peter Zijlstra; > x...@kernel.org; linux-kernel@vger.kernel.org; Pan, Jacob jun > Subject: Re: Hi, Ingo,

RE: Hi, Ingo, would you please help drop the TSC MSR calibration patch

Hi, > -Original Message- > From: Pan, Jacob jun > Sent: Tuesday, July 12, 2016 5:19 AM > To: Ingo Molnar > Cc: Chen, Yu C; 'Len Brown'; Jacob Pan; H. Peter Anvin; Peter Zijlstra; > x...@kernel.org; linux-kernel@vger.kernel.org; Pan, Jacob jun > Subject: Re: Hi, Ingo,

Re: Hi, Ingo, would you please help drop the TSC MSR calibration patch

On Mon, 11 Jul 2016 21:31:04 +0200 Ingo Molnar wrote: > > * Jacob Pan wrote: > > > On Mon, 11 Jul 2016 07:59:19 -0700 > > "Chen, Yu C" wrote: > > > > > Currently it is in your x86/timer tree: > > > > > > commit

Re: Hi, Ingo, would you please help drop the TSC MSR calibration patch

On Mon, 11 Jul 2016 21:31:04 +0200 Ingo Molnar wrote: > > * Jacob Pan wrote: > > > On Mon, 11 Jul 2016 07:59:19 -0700 > > "Chen, Yu C" wrote: > > > > > Currently it is in your x86/timer tree: > > > > > > commit fc273eeef314cdaf0ac992b400d126f8184a4d1c > > > Author: Len Brown > > > Date:

Re: Hi, Ingo, would you please help drop the TSC MSR calibration patch

* Jacob Pan wrote: > On Mon, 11 Jul 2016 07:59:19 -0700 > "Chen, Yu C" wrote: > > > Currently it is in your x86/timer tree: > > > > commit fc273eeef314cdaf0ac992b400d126f8184a4d1c > > Author: Len Brown > > Date: Fri Jun 17

Re: Hi, Ingo, would you please help drop the TSC MSR calibration patch

* Jacob Pan wrote: > On Mon, 11 Jul 2016 07:59:19 -0700 > "Chen, Yu C" wrote: > > > Currently it is in your x86/timer tree: > > > > commit fc273eeef314cdaf0ac992b400d126f8184a4d1c > > Author: Len Brown > > Date: Fri Jun 17 01:22:49 2016 -0400 > > > > x86/tsc_msr: Extend to include

Re: Hi, Ingo, would you please help drop the TSC MSR calibration patch

On Mon, 11 Jul 2016 07:59:19 -0700 "Chen, Yu C" wrote: > Currently it is in your x86/timer tree: > > commit fc273eeef314cdaf0ac992b400d126f8184a4d1c > Author: Len Brown > Date: Fri Jun 17 01:22:49 2016 -0400 > > x86/tsc_msr: Extend to include

Re: Hi, Ingo, would you please help drop the TSC MSR calibration patch

On Mon, 11 Jul 2016 07:59:19 -0700 "Chen, Yu C" wrote: > Currently it is in your x86/timer tree: > > commit fc273eeef314cdaf0ac992b400d126f8184a4d1c > Author: Len Brown > Date: Fri Jun 17 01:22:49 2016 -0400 > > x86/tsc_msr: Extend to include Intel Core Architecture > > > Previously

Re: Hi

Dear Client Do you need a quick loan to establish, for estate license, to buy car, house, no problem we offer Personal loan, Business loan Student loan and General loan, Why not take off for a little while, get away and enjoy yourself we also offer loan for vacation. For more information

Re: Hi

Dear Client Do you need a quick loan to establish, for estate license, to buy car, house, no problem we offer Personal loan, Business loan Student loan and General loan, Why not take off for a little while, get away and enjoy yourself we also offer loan for vacation. For more information

Re: Hi

Dear Client Do you need a quick loan to establish, for estate license, to buy car, house, no problem we offer Personal loan, Business loan Student loan and General loan, Why not take off for a little while, get away and enjoy yourself we also offer loan for vacation. For more information

Re: Hi

Dear Client Do you need a quick loan to establish, for estate license, to buy car, house, no problem we offer Personal loan, Business loan Student loan and General loan, Why not take off for a little while, get away and enjoy yourself we also offer loan for vacation. For more information

Re: hi-res mtime userspace interface

Stephen Hemminger wrote: Look at stat. Thanks. OK that was what I wanted. I hadn't looked further than man 2 stat - I think the stat man page needs an update. In /usr/include/bits/stat.h: struct stat { __dev_t st_dev; /* Device. */ ... #ifdef __USE_MISC /*

Re: hi-res mtime userspace interface

On Sun, 20 Jan 2008 21:09:52 +0800 Michael Clark <[EMAIL PROTECTED]> wrote: > Is there an existing linux userspace interface for accessing the > microsecond or nanosecond level (a|m|c)times of filesystems that support > them (e.g. ext4, xfs)? and possibly also the generation counters used by >

Re: hi-res mtime userspace interface

On Sun, 20 Jan 2008 21:09:52 +0800 Michael Clark [EMAIL PROTECTED] wrote: Is there an existing linux userspace interface for accessing the microsecond or nanosecond level (a|m|c)times of filesystems that support them (e.g. ext4, xfs)? and possibly also the generation counters used by NFS.

Re: hi-res mtime userspace interface

Stephen Hemminger wrote: Look at stat. Thanks. OK that was what I wanted. I hadn't looked further than man 2 stat - I think the stat man page needs an update. In /usr/include/bits/stat.h: struct stat { __dev_t st_dev; /* Device. */ ... #ifdef __USE_MISC /*

Re: Hi, I have one question about rt_mutex.

Li Yu wrote: > > However, I found the sys_futex() do not use rt_mutex, so what's mean of the > user futex you said? > Even, I have not found any usage for rt_mutex in kernel code. Or, some > beautiful story will happen in future? > Just need to look a little deeper :-) sys_futex calls

Re: Hi, I have one question about rt_mutex.

Li Yu wrote: However, I found the sys_futex() do not use rt_mutex, so what's mean of the user futex you said? Even, I have not found any usage for rt_mutex in kernel code. Or, some beautiful story will happen in future? Just need to look a little deeper :-) sys_futex calls do_futex

Re: Hi, I have one question about rt_mutex.

Steven Rostedt wrote: > Li Yu wrote: > >>> Now since mutexes can be defined by user-land applications, we don't >>> >> want a DOS >> >>> type of application that nests large amounts of mutexes to create a large >>> PI chain, and have the code holding spin locks while looking at a

Re: Hi, I have one question about rt_mutex.

Li Yu wrote: >> Now since mutexes can be defined by user-land applications, we don't > want a DOS >> type of application that nests large amounts of mutexes to create a large >> PI chain, and have the code holding spin locks while looking at a large >> amount of data. So to prevent this, the

Re: Hi, I have one question about rt_mutex.

On Thu, 10 May 2007, Li Yu wrote: Hi, Steven. Nice to meet you again. I have read the rt-mutex-design.txt that you wrote. That is excellent description of rt_mutex. But I have a question for rt_mutex. As you said: Now since mutexes can be defined by user-land applications, we don't

Re: Hi, I have one question about rt_mutex.

On Thu, 10 May 2007, Li Yu wrote: Hi, Steven. Nice to meet you again. I have read the rt-mutex-design.txt that you wrote. That is excellent description of rt_mutex. But I have a question for rt_mutex. As you said: Now since mutexes can be defined by user-land applications, we don't

Re: Hi, I have one question about rt_mutex.

Li Yu wrote: Now since mutexes can be defined by user-land applications, we don't want a DOS type of application that nests large amounts of mutexes to create a large PI chain, and have the code holding spin locks while looking at a large amount of data. So to prevent this, the implementation

Re: Hi, I have one question about rt_mutex.

Steven Rostedt wrote: Li Yu wrote: Now since mutexes can be defined by user-land applications, we don't want a DOS type of application that nests large amounts of mutexes to create a large PI chain, and have the code holding spin locks while looking at a large amount of

Re: hi, should these code is a problem in nfs system clnt.c?

On Tue, 2006-12-12 at 09:00 -0500, Peter Staubach wrote: > linuxer linuxer wrote: > > Hi, everyone: > > I am a newbie, if my question waste your time, I > > am sorry for that. > > > > In clnt.c file ,call_timeout function: > > I suggest the code that judge whether the network > >

Re: hi, should these code is a problem in nfs system clnt.c?

linuxer linuxer wrote: Hi, everyone: I am a newbie, if my question waste your time, I am sorry for that. In clnt.c file ,call_timeout function: I suggest the code that judge whether the network link status is down should be added, won't they? I tested it with one Ethernet

Re: hi, should these code is a problem in nfs system clnt.c?

linuxer linuxer wrote: Hi, everyone: I am a newbie, if my question waste your time, I am sorry for that. In clnt.c file ,call_timeout function: I suggest the code that judge whether the network link status is down should be added, won't they? I tested it with one Ethernet

Re: hi, should these code is a problem in nfs system clnt.c?

On Tue, 2006-12-12 at 09:00 -0500, Peter Staubach wrote: linuxer linuxer wrote: Hi, everyone: I am a newbie, if my question waste your time, I am sorry for that. In clnt.c file ,call_timeout function: I suggest the code that judge whether the network link status is

Re: Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

Just to follow up to myself, after futher testing, it looks like it's an SMP-related problem. I'm not yet sure if it's an SMP-Via chipset problem or just an SMP problem. I've heard from two people with this same problem. I think one of them has a Via chipset and I'm not sure about the other

Re: Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

Just to follow up to myself, after futher testing, it looks like it's an SMP-related problem. I'm not yet sure if it's an SMP-Via chipset problem or just an SMP problem. I've heard from two people with this same problem. I think one of them has a Via chipset and I'm not sure about the other

Re: Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

I think I've seen this same problem, at least with regards to USB printing. Yesterday, I traced the problem down to a patch to usb-uhci.c in the transition from 2.4.3 to 2.4.4. The problem persists today. A work around for this problem is to use the alternate UHCI driver (uhci.o). What

Re: Hi all, a strange full lock in SMP-kernel 2.4.6 and 2.4.5

I think I've seen this same problem, at least with regards to USB printing. Yesterday, I traced the problem down to a patch to usb-uhci.c in the transition from 2.4.3 to 2.4.4. The problem persists today. A work around for this problem is to use the alternate UHCI driver (uhci.o). What

Re: Hi memory support in 2.4 not working correctly.

On Wed, 17 Jan 2001, Micah Gorrell wrote: > I have a compaq 8 way server with 4 gigs of memory. I am running 2.4.0 and > everything works just fine (except the gig - I'm still fighting with that) > The only strange thing that I am seeing is that I only see 3.3 gigs of > memory instead of the

Re: Hi memory support in 2.4 not working correctly.

On Wed, 17 Jan 2001, Micah Gorrell wrote: I have a compaq 8 way server with 4 gigs of memory. I am running 2.4.0 and everything works just fine (except the gig - I'm still fighting with that) The only strange thing that I am seeing is that I only see 3.3 gigs of memory instead of the full