IP Library Patent Application 10533735
Patent Application
App. No. 10/533,735

Method and device for persistent-memory mangement

Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US None
App. No.
10/533,735
Filed
May 4, 2005
Art Unit
2186
USPC
711/170
Abstract

The present invention relates to a method for managing memory space of a persistent-memory device and to a memory management device. The memory management method of the invention comprises a step of allocating (S 14 ) at least one first part of said memory space to a file system ( 74 ) upon request from said file system ( 74 ) or from an application ( 70 ). The method and the device of the present invention enable a dynamical allocation of persistent-memory space to a file system. This way, the memory space of a persistent memory is effectively used also for write-caching. At the same time, write-caching and storing steps can be accelerated.

Claims (31)

1 . A memory management device for managing a memory space of at least one persistent-memory device, comprising a memory allocation unit adapted to communicate with at least one application device and to allocate at least one first part of said memory space to said application device, wherein said allocation unit is further adapted to communicate with at least one file system device, and to allocate on request from said application device or from said file system device said first part of said memory space to said file system.

2 . A memory management device according to claim 1 , wherein said memory allocation unit is adapted to maintain a memory allocation table at a current status, said memory allocation table assigning at least one memory address representing a defined part of said memory space to either said application device or to said file system device.

3 . A memory management device according to claim 2 , further comprising a processor and a memory, wherein said memory allocation unit is implemented in the form of at least one first executable file contained in said memory.

4 . A memory management device according to claim 3 , wherein said memory is a persistent-memory device, in particular said persistent-memory device.

5 . A file system device, comprising a file allocation unit adapted to maintain a file allocation table at a current status, said file allocation table assigning at least one disk space address to at least one file, wherein said file allocation unit is adapted to communicate with a memory management device that is related to a persistent-memory device and to include an address of at least one first memory space of said persistent-memory device in the maintenance of said file allocation table.

6 . A file system device according to claim 5 , further comprising a processor and a memory, wherein said file allocation unit is implemented in the form of at least one second executable file contained in said memory.

7 . An application device, comprising a persistent-memory device connected to a processor, and a data management unit adapted to manipulate data in said persistent memory device, wherein said data management unit is adapted to write at least one third executable file to said persistent memory device, or to provide the file system with a reference to at least on third executable file in said file system, such that by executing said third executable file said processor is adapted to transform said data into a predetermined data-sequence form.

8 . An application device according to claim 7 , wherein said data management unit is provided in the form of least one fourth executable file in a memory, particularly, in said persistent memory.

9 . A storage medium containing said first executable file according to claim 3 .

10 . A data processing system, comprising a memory management device for managing a memory space of at least one persistent-memory device, comprising a memory allocation unit adapted to communicate with at least one application device and to allocate at least one first part of said memory space to said application device, wherein said allocation unit is further adapted to communicate with at least one file system device, and to allocate on request from said application device or from said file system device said first part of said memory space to said file system.

11 . A method for managing memory space of a persistent-memory device, comprising a step of allocating at least one first part of said memory space to a file system device upon request from said file system device or from an application device.

12 . A method according to claim 11 , wherein said allocating step comprises a step of blocking a writing access to said first part of said memory space.

13 . A method according to claim 12 , wherein said allocating step comprises a step of giving away to said file system device the power of reading access to said first part of said memory space.

14 . A method according to claim 11 , comprising a step of deallocating said first part of said memory space to a memory management device.

15 . A method according to claim 11 , wherein said allocating step or said deallocating step comprises transmitting an address range defining said first part of said memory space from said memory management device to said file system device or, respectively, vice versa.

16 . A method according to claim 14 , wherein said deallocating step is performed for said first part of said memory space given the condition that first data contained in said first part of said memory space is stored in the form of file data in a second part of said memory space, said file data having a predetermined file structure, and

that said second part of said memory space is allocated to said file system device.

17 . A method according to claim 16 , wherein said deallocating step is performed for said second part of said memory space given the condition that said file data has been written to a secondary storage medium.

18 . A method for write-caching first data worked on by an application, said first data being contained in a first part of a memory space of a persistent-memory device, comprising a step of performing a memory managing method according to claim 17 .

19 . A write-caching method according to claim 18 , comprising, after said allocating step, a step of sending a confirmation message from said file system device to said application device.

20 . A write-caching method according to claim 18 , wherein said first data is a copy of third data contained in a third part of said memory space, said write-caching method comprising, before performing said memory managing method, a step of copying said third data to said first memory space.

21 . A write-caching method according to claim 18 , comprising the steps of

allocating a fourth part of said memory space to said application device for an executable file or dynamic link library that is adapted to converting said first data into file data

writing said executable file or dynamic link library to said fourth part of said memory space

allocating said fourth part of said memory space to said file system device.

22 . A write-caching method according to claim 21 , comprising a step of transforming said first data into said file data with the aid of said executable file or said dynamic link library.

23 . A write-caching method according to claim 22 , wherein said transforming step is initiated by said file system device.

24 . A write-caching method according to claim 23 , comprising, after said transforming step, a step of deallocating said fourth part of said memory space to said memory management device.

25 . A method for saving data worked on by an application device to a file on a secondary storage medium, comprising the steps of

Performing a write-caching method according to claim 18 ,

Writing said file data to said secondary storage medium.

Assignments (5)
RELEASE OF SECURITY INTEREST Recorded Oct 25, 2023
From: NXP B.V.
To: CROCUS TECHNOLOGY INC.
Reel/Frame 065334/0488 →
CORRECTIVE ASSIGNMENT TO CORRECT THE THE SPELLING OF THE CONVEYING PARTY NAME AND ADDRESS ON THE DOCUMENT. PREVIOUSLY RECORDED AT REEL: 02722 FRAME: 0049. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Oct 25, 2023
From: CROCUS TECHNOLOGY INC.
To: NXP B.V.
Reel/Frame 065345/0304 →
LIEN Recorded Nov 14, 2011
From: CROCUS TECHNOLOGY, INC.
To: NXP B.V.
Reel/Frame 027222/0049 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 17, 2007
From: KONINKLIJKE PHILIPS ELECTRONICS N.V.
To: NXP B.V.
Reel/Frame 019719/0843 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 4, 2005
From: JOCHEMSEN, ROBERT; BODLAENDER, MAARTEN PETER; FONTIJN, WILHELMUS FRANCISCUS JOHANNES; DENISSEN, ADRIANUS JOHANNES MARIA; LAMBERT, NICOLAAS
To: KONINKLIJKE PHILIPS ELECTRONICS, N.V.
Reel/Frame 017122/0665 →