Patch Detail
get:
Show a patch.
patch:
Update a patch.
put:
Update a patch.
GET /api/1.0/patches/140033/?format=api
{ "id": 140033, "url": "http://patchwork.dpdk.org/api/1.0/patches/140033/?format=api", "project": { "id": 1, "url": "http://patchwork.dpdk.org/api/1.0/projects/1/?format=api", "name": "DPDK", "link_name": "dpdk", "list_id": "dev.dpdk.org", "list_email": "dev@dpdk.org", "web_url": "http://core.dpdk.org", "scm_url": "git://dpdk.org/dpdk", "webscm_url": "http://git.dpdk.org/dpdk" }, "msgid": "<20240513155911.31872-5-nandinipersad361@gmail.com>", "date": "2024-05-13T15:59:06", "name": "[4/9] doc: reword service cores section in prog guide", "commit_ref": null, "pull_url": null, "state": "new", "archived": false, "hash": "b44b550b23efa75b35501e330416b3517b98459c", "submitter": { "id": 3325, "url": "http://patchwork.dpdk.org/api/1.0/people/3325/?format=api", "name": "Nandini Persad", "email": "nandinipersad361@gmail.com" }, "delegate": { "id": 1, "url": "http://patchwork.dpdk.org/api/1.0/users/1/?format=api", "username": "tmonjalo", "first_name": "Thomas", "last_name": "Monjalon", "email": "thomas@monjalon.net" }, "mbox": "http://patchwork.dpdk.org/project/dpdk/patch/20240513155911.31872-5-nandinipersad361@gmail.com/mbox/", "series": [ { "id": 31913, "url": "http://patchwork.dpdk.org/api/1.0/series/31913/?format=api", "date": "2024-05-13T15:59:02", "name": "reowrd in prog guide", "version": 1, "mbox": "http://patchwork.dpdk.org/series/31913/mbox/" } ], "check": "success", "checks": "http://patchwork.dpdk.org/api/patches/140033/checks/", "tags": {}, "headers": { "Return-Path": "<dev-bounces@dpdk.org>", "X-Original-To": "patchwork@inbox.dpdk.org", "Delivered-To": "patchwork@inbox.dpdk.org", "Received": [ "from mails.dpdk.org (mails.dpdk.org [217.70.189.124])\n\tby inbox.dpdk.org (Postfix) with ESMTP id B85164401C;\n\tMon, 13 May 2024 18:02:04 +0200 (CEST)", "from mails.dpdk.org (localhost [127.0.0.1])\n\tby mails.dpdk.org (Postfix) with ESMTP id 1173940A79;\n\tMon, 13 May 2024 18:01:41 +0200 (CEST)", "from mail-pf1-f175.google.com (mail-pf1-f175.google.com\n [209.85.210.175])\n by mails.dpdk.org (Postfix) with ESMTP id D97B140687\n for <dev@dpdk.org>; Mon, 13 May 2024 17:59:36 +0200 (CEST)", "by mail-pf1-f175.google.com with SMTP id\n d2e1a72fcca58-6f44dd41a5cso4593278b3a.0\n for <dev@dpdk.org>; Mon, 13 May 2024 08:59:36 -0700 (PDT)", "from localhost.localdomain (syn-076-032-089-124.res.spectrum.com.\n [76.32.89.124]) by smtp.gmail.com with ESMTPSA id\n d2e1a72fcca58-6f4d2aa16dfsm7715078b3a.93.2024.05.13.08.59.35\n (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256);\n Mon, 13 May 2024 08:59:35 -0700 (PDT)" ], "DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=gmail.com; s=20230601; t=1715615976; x=1716220776; darn=dpdk.org;\n h=content-transfer-encoding:mime-version:references:in-reply-to\n :message-id:date:subject:cc:to:from:from:to:cc:subject:date\n :message-id:reply-to;\n bh=Vw3KutvrNMUJxXkyW/HjN0/L1LNmCWrtE2KRtp1LAzQ=;\n b=I5A2rw8cV+P98BI62hEO3lxWOqCeFm5nvzqEOULjRYLXEMAZXjN9QBPmaBSWg2WFws\n 8d8rd70jUz1HU46EMBie0jBBy/P1Il9zP/nrN51a2UYPUEo1GhMUPyfbqt+HyQN+vOdQ\n iNsuZP5t4RGYhpStxX6n2LmMancdXkgzMWLMbNsyFEGWIdwGh14fQwQ1v1bBaL1l7dnH\n 72C3bSF/mBDVMNEQDe7rj5MjDskfZpvH8iFNMxVCzBlR5Y2NrIOTI9sCwXLGHzVLUssl\n doaSMj1Jn+7T7CDACcUV+9e4lvJNuZgMa4xuB4DK5aUQ0qRDbugyJMT4PGH6z1BHdWvo\n 9b4g==", "X-Google-DKIM-Signature": "v=1; a=rsa-sha256; c=relaxed/relaxed;\n d=1e100.net; s=20230601; t=1715615976; x=1716220776;\n h=content-transfer-encoding:mime-version:references:in-reply-to\n :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc\n :subject:date:message-id:reply-to;\n bh=Vw3KutvrNMUJxXkyW/HjN0/L1LNmCWrtE2KRtp1LAzQ=;\n b=OFdhXpQHYXhmgnnBpI50iCKF45RS0LrvYtdHI3u1DQ8D/HJ6qXXp8YmR0O+BYEird7\n DO/kWm+D6BGB6iMSLw7v11iG6y2kI9iSUyNx7Tuy0/Fhog9EtqaYq0Gq3jSgO9sDd5HT\n e5LyysIOvvBYeAQWTzKpQKX3yFt+GZCPwClZptPkdw2BWfJ29xFGjt7Qe9XFrSK/uZzR\n cMnxu6upgx9duW+e3kIYZg0pPeM5FuVEqcfAWvyVryPCb4jjk5LPKxJ/8na4Q/flBaNo\n j+KKgFyXQDT0EKs+B1ZxftR9V4ZIIsB+rO556ywYJawrzTrc4xXFpC8SNR1wDYtJZzHx\n qKsQ==", "X-Gm-Message-State": "AOJu0Yy3/6TjLPVS7kvECEMbV1kfTKnoTPSDZ3B9MV8FzEJHHRPrcPmb\n W9ukpsAJVXnCARpK6p5fnSHmQQT4qG50S9OBx52PMIQaE9KE5LRE0VZD+A==", "X-Google-Smtp-Source": "\n AGHT+IHOKee2PxZ93se+yhmP3bf/ViXHUqmHKg1ToISWRVdE2Wyq+qChqlHosTmG6eJSM/WYwXUcKQ==", "X-Received": "by 2002:a05:6a20:f397:b0:1af:ad46:cd4a with SMTP id\n adf61e73a8af0-1afde09f3c5mr11155372637.12.1715615975800;\n Mon, 13 May 2024 08:59:35 -0700 (PDT)", "From": "Nandini Persad <nandinipersad361@gmail.com>", "To": "dev@dpdk.org", "Cc": "Harry van Haaren <harry.van.haaren@intel.com>", "Subject": "[PATCH 4/9] doc: reword service cores section in prog guide", "Date": "Mon, 13 May 2024 08:59:06 -0700", "Message-Id": "<20240513155911.31872-5-nandinipersad361@gmail.com>", "X-Mailer": "git-send-email 2.34.1", "In-Reply-To": "<20240513155911.31872-1-nandinipersad361@gmail.com>", "References": "<20240513155911.31872-1-nandinipersad361@gmail.com>", "MIME-Version": "1.0", "Content-Transfer-Encoding": "8bit", "X-Mailman-Approved-At": "Mon, 13 May 2024 18:01:34 +0200", "X-BeenThere": "dev@dpdk.org", "X-Mailman-Version": "2.1.29", "Precedence": "list", "List-Id": "DPDK patches and discussions <dev.dpdk.org>", "List-Unsubscribe": "<https://mails.dpdk.org/options/dev>,\n <mailto:dev-request@dpdk.org?subject=unsubscribe>", "List-Archive": "<http://mails.dpdk.org/archives/dev/>", "List-Post": "<mailto:dev@dpdk.org>", "List-Help": "<mailto:dev-request@dpdk.org?subject=help>", "List-Subscribe": "<https://mails.dpdk.org/listinfo/dev>,\n <mailto:dev-request@dpdk.org?subject=subscribe>", "Errors-To": "dev-bounces@dpdk.org" }, "content": "made minor syntax changes to section 8 of programmer's guide, service cores\n\nSigned-off-by: Nandini Persad <nandinipersad361@gmail.com>\n---\n doc/guides/prog_guide/service_cores.rst | 32 ++++++++++++-------------\n 1 file changed, 16 insertions(+), 16 deletions(-)", "diff": "diff --git a/doc/guides/prog_guide/service_cores.rst b/doc/guides/prog_guide/service_cores.rst\nindex d4e6c3d6e6..59da3964bf 100644\n--- a/doc/guides/prog_guide/service_cores.rst\n+++ b/doc/guides/prog_guide/service_cores.rst\n@@ -4,38 +4,38 @@\n Service Cores\n =============\n \n-DPDK has a concept known as service cores, which enables a dynamic way of\n-performing work on DPDK lcores. Service core support is built into the EAL, and\n-an API is provided to optionally allow applications to control how the service\n+DPDK has a concept known as service cores. Service cores enable a dynamic way of\n+performing work on DPDK lcores. Service core support is built into the EAL.\n+An API is provided to give you the option of allowing applications to control how the service\n cores are used at runtime.\n \n-The service cores concept is built up out of services (components of DPDK that\n+The service cores concept is built out of services (components of DPDK that\n require CPU cycles to operate) and service cores (DPDK lcores, tasked with\n running services). The power of the service core concept is that the mapping\n-between service cores and services can be configured to abstract away the\n+between service cores and services can be configured to simplify the\n difference between platforms and environments.\n \n-For example, the Eventdev has hardware and software PMDs. Of these the software\n+For example, the Eventdev has hardware and software PMDs. Of these the software,\n PMD requires an lcore to perform the scheduling operations, while the hardware\n PMD does not. With service cores, the application would not directly notice\n-that the scheduling is done in software.\n+that the scheduling is done in the software.\n \n For detailed information about the service core API, please refer to the docs.\n \n Service Core Initialization\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n-There are two methods to having service cores in a DPDK application, either by\n+There are two methods to having service cores in a DPDK application: by\n using the service coremask, or by dynamically adding cores using the API.\n-The simpler of the two is to pass the `-s` coremask argument to EAL, which will\n-take any cores available in the main DPDK coremask, and if the bits are also set\n-in the service coremask the cores become service-cores instead of DPDK\n+The simpler of the two is to pass the `-s` coremask argument to the EAL, which will\n+take any cores available in the main DPDK coremask. If the bits are also set\n+in the service coremask, the cores become service-cores instead of DPDK\n application lcores.\n \n Enabling Services on Cores\n ~~~~~~~~~~~~~~~~~~~~~~~~~~\n \n-Each registered service can be individually mapped to a service core, or set of\n+Each registered service can be individually mapped to a service core, or a set of\n service cores. Enabling a service on a particular core means that the lcore in\n question will run the service. Disabling that core on the service stops the\n lcore in question from running the service.\n@@ -48,8 +48,8 @@ function to run the service.\n Service Core Statistics\n ~~~~~~~~~~~~~~~~~~~~~~~\n \n-The service core library is capable of collecting runtime statistics like number\n-of calls to a specific service, and number of cycles used by the service. The\n+The service core library is capable of collecting runtime statistics like the number\n+of calls to a specific service, and the number of cycles used by the service. The\n cycle count collection is dynamically configurable, allowing any application to\n profile the services running on the system at any time.\n \n@@ -58,9 +58,9 @@ Service Core Tracing\n \n The service core library is instrumented with tracepoints using the DPDK Trace\n Library. These tracepoints allow you to track the service and logical cores\n-state. To activate tracing when launching a DPDK program it is necessary to use the\n+state. To activate tracing when launching a DPDK program, it is necessary to use the\n ``--trace`` option to specify a regular expression to select which tracepoints\n-to enable. Here is an example if you want to only specify service core tracing::\n+to enable. Here is an example if you want to specify only service core tracing::\n \n ./dpdk/examples/service_cores/build/service_cores --trace=\"lib.eal.thread*\" --trace=\"lib.eal.service*\"\n \n", "prefixes": [ "4/9" ] }