search for: address_s

Displaying 12 results from an estimated 12 matches for "address_s".

Did you mean: address_r
2008 Mar 13
3
newbie question: pxelinux.cfg/default question
Hello all, I understand that during PXE boot, it goes into the pxelinux.cfg and it states: 1. "it will search for the config file using its own IP address in upper case hexadecimal, e.g. 192.0.2.91 -> C000025B (you can use the included progam "gethostip" to compute the hexadecimal IP address for any host.) If that file is not found, it will remove one hex digit and try
2008 Jun 28
2
[LLVMdev] need to store the address of a variable
Hello everybody, my problem is, that I want to get an array of pointers to all local variables in a function. This array will be used for transfering these Variables to another execution engine. I've code which generates this array, and a pointer to the target field of the array. name = variables.fname + "_pointerArray"; Instruction* pointerArray = new
2003 Nov 25
1
About sound modules in Asterisk. And call gnophone-asterisk-h323
Hi, First at alll, I beg your pardon because maybe I explained bad my questions (because my low level english) I have asterisk 0.5.0, asterisk-oh323-0.5.6, openh323-1.12.2 and pwlib 1.5.2 compiled and installed. I have modules alsa 0.9.8 compiled and installed My PC has an audio card ac97 chipset intel i810 in its motherboard. I want to use asterisk in this way: |PC linux | --ethernet--
2008 Jun 28
0
[LLVMdev] need to store the address of a variable
Paul Arndt wrote: > Hello everybody, > > my problem is, that I want to get an array of pointers to all local variables > in a function. This array will be used for transfering these Variables to > another execution engine. > > I've code which generates this array, and a pointer to the target field of the > array. > > name = variables.fname +
2003 Nov 16
0
[LLVMdev] Packages
On Sun, 2003-11-16 at 17:13, Chris Lattner wrote: > > The point here is that XPL needs to keep track of what a given variable > > represents at the source level. If the compiler sees a map that is > > initially small it might represent it in LLVM assembly as a vector of > > pairs. Later on, it gets optimized into being a hash table. In order to > > do that and keep
2003 Nov 16
3
[LLVMdev] Packages
> The point here is that XPL needs to keep track of what a given variable > represents at the source level. If the compiler sees a map that is > initially small it might represent it in LLVM assembly as a vector of > pairs. Later on, it gets optimized into being a hash table. In order to > do that and keep track of things, I need to know that the vector of > pairs is
2007 Apr 18
4
[patch 3/9] Guest page hinting: volatile page cache.
...d_debug_level; * sure the page is locked and that nobody else uses it - or that usage * is safe. The caller must hold a write_lock on the mapping's tree_lock. */ -void __remove_from_page_cache(struct page *page) +void inline __remove_from_page_cache_nocheck(struct page *page) { struct address_space *mapping = page->mapping; @@ -127,6 +127,28 @@ void __remove_from_page_cache(struct pag mapping->nrpages--; __dec_zone_page_state(page, NR_FILE_PAGES); } + +void __remove_from_page_cache(struct page *page) +{ + /* + * Check if the discard fault handler already removed + * the pag...
2007 Apr 18
4
[patch 3/9] Guest page hinting: volatile page cache.
...d_debug_level; * sure the page is locked and that nobody else uses it - or that usage * is safe. The caller must hold a write_lock on the mapping's tree_lock. */ -void __remove_from_page_cache(struct page *page) +void inline __remove_from_page_cache_nocheck(struct page *page) { struct address_space *mapping = page->mapping; @@ -127,6 +127,28 @@ void __remove_from_page_cache(struct pag mapping->nrpages--; __dec_zone_page_state(page, NR_FILE_PAGES); } + +void __remove_from_page_cache(struct page *page) +{ + /* + * Check if the discard fault handler already removed + * the pag...
2007 Jun 28
6
[patch 0/6] resend: guest page hinting version 5.
Greetings, after Carsten pitched CMM2 on the kvm mini summit here is a repost of version 5 of the guest page hinting patches. The code is still the same but has been adapted to the latest git level. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.
2007 Jun 28
6
[patch 0/6] resend: guest page hinting version 5.
Greetings, after Carsten pitched CMM2 on the kvm mini summit here is a repost of version 5 of the guest page hinting patches. The code is still the same but has been adapted to the latest git level. -- blue skies, Martin. "Reality continues to ruin my life." - Calvin.
2007 May 11
6
[patch 0/6] [rfc] guest page hinting version 5
After way to many months here is the fifth version of the guest page hinting patches. Compared to version four a few improvements have been added: - Avoid page_host_discards() calls outside of page-states.h - The discard list is now implemented via the page_free_discarded hook and architecture specific code. - PG_state_change page flag has been replaced with architecture specficic
2007 May 11
6
[patch 0/6] [rfc] guest page hinting version 5
After way to many months here is the fifth version of the guest page hinting patches. Compared to version four a few improvements have been added: - Avoid page_host_discards() calls outside of page-states.h - The discard list is now implemented via the page_free_discarded hook and architecture specific code. - PG_state_change page flag has been replaced with architecture specficic